The default is now not set, which allows for opt-in; however, that would still allow and end-user to specify role=navigation with a nav tag. ... which is invalid. I'm not sure if we should force HTML5 compliance (e.g. end users would be frustrated that we drop a potential prop in this case where it's invalid) .... OR we can leave as is, where the defaults are empty, any explicit props will override ... and we could potentially update the default role to show for non nav elements if one is not specified.

@eddywashere Thoughts?

ping @eddywashere