Per my goal of basic ARIA support for mozilla.com (https://wiki.mozilla.org/Webdev:WAI-ARIA#Basic_ARIA_Support).
r52484 adds navigation, search and contentinfo roles to all pages. Updating all pages to add role="main" to main content blocks may be unattainable considering the # of files and dangers of a mass search-and-replace.
Next steps here? Or are we done?
(In reply to comment #2)
> Next steps here? Or are we done?
Next step would be updating all locales to add role="main" their main content blocks. I'm not sure of a good/reliable method of doing this easily though.
<div role="main" id="doc">
<div role="menubar" id="nav-main">
* Not "navigation" because it has dropdown menus
* role="menu" and role="menuitem" will follow
* implementing keyboard navigation is appreciated
<ul role="navigation" id="footer-menu">
> * implementing keyboard navigation is appreciated
Err, www.mozilla.com has already implemented this stuff.
<div id="header" role="banner">
<div id="footer-menu" role="presentation">
because it's a dup of #nav-main and should not be read again by screen readers.
I'll make a patch for the nova branch in good time...
Just FYI: ALA has published articles on ARIA, worth reading.
Doing a bit of bug housekeeping here and came across this.
Closing for now. If you think this is still important to fix, and applies to the current mozilla.com, please re-open. Thanks!
a11y is important.
Absolutely. At least the landmark roles -- banner and main -- should be added.
And the pager-with-tabs should have the tablist, tab and tabpanel roles.
We have widely used ARIA roles at http://mozilla.jp/
You can test the ARIA implementation with NVDA, an open source screen reader.
I'll make a patch for Bedrock.