We're adding new content to our page that describes the accessibility options available at a destination. The user may make accessibility requests via checkbox inputs (bathroom, hearing-impaired equipment, etc.) but we're now providing a disclaimer for things that cannot be reserved online (braille, accessible parking, etc.)

As this is geared specifically towards people with accessibility needs, what's the best way to call out this content to a screen reader?


Create jump to content links http://webaim.org/techniques/css/invisiblecontent/

Use proper HTML5 tags relevant to the content. https://stackoverflow.com/questions/19595719/html5-main-element-versus-aria-landmark-role-main Use Aria Landmark roles. http://a11yproject.com/posts/aria-landmark-roles/

More information on Aria attributes and usages http://webdesign.about.com/od/accessibility/a/wai-aria.htm

  • These are excellent links, and I am familiar with semantic tags and ARIA. Do you know of an appropriate ARIA role to call out visible, non-interactive content? – cowcat Aug 5 '14 at 19:38
  • The main and article roles seems to be the absolute strongest of them all. – Chris Marisic Aug 5 '14 at 19:42

I have used aria-label and aria-labelledby. Though i am not an expert in AX

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.