search

givepulse / knowbilitywarriors

Web Accessibility Website work for Accessible Housing Austin
0 stars 1 forks source link

All content must reside within a WAI-ARIA landmark or labelled region role. #42

Closed mehdia closed 10 years ago

mehdia commented 10 years ago

Page: story, housing, our story, facts, contact us, donate

On element: /html/body/header/h1 /html/body/footer/address/p

Solution: All content must reside within a WAI-ARIA landmark or labelled region role to facilitate page navigation by screen reader users.

Example 1: a WAI-ARIA main role is specified on the element containing the main content of a Web page.

         <div role="main">
            Main content of Web page...
         </div>

Example 2: a WAI-ARIA navigation role is specified on the element containing the left navigation area of a Web page.

         <div role="navigation">
            Left navigation area links...
         </div>

Example 3: a WAI-ARIA search role is specified on the element containing the search area of a Web page.

     <div role="search">
            Search area of Web page...
     </div>

Example 4: a page author has determined that none of the standard WAI-ARIA landmarks are appropriate for a specific area of page content. Therefore, the author places a WAI-ARIA region role on the element containing the content and labels the region with an aria-label property.

     <div role="region" aria-label="Realtime message log">
            None of the standard WAI-ARIA landmarks are appropriate for the content in this area, so marking it with a region role...
     </div>
slauriat commented 10 years ago

Which page has what content outside of a landmark?

slauriat commented 10 years ago

Just noticed the top of the bug. Do headers and footers not count as landmarks?

mehdia commented 10 years ago

No they don't. Like you have role = main in your

, you would bee role = contentinfo for
slauriat commented 10 years ago

Okay, cool. Thanks for the explanation! Fixed.

mehdia commented 10 years ago

superb !