Blog

Archive for the "Accessibility Best Practices" Topic

Accessibility Considerations for Localization

Posted on:

Localization is the process of translating a product into different languages or adapting a product for a specific country or region.   When localization is performed on web content, information such as alternatives used by people with disabilities may inadvertently be overlooked.  When pages are localized, language teams often update strings of content and view the visual changes on the web page.  Some accessibility information is not visible on a web page but still must be localized, e.g. alternative text for images and text positioned off-screen for screen readers. Localization teams need procedures and tools to help them find this accessibility… Read More

Accessibility Basics Series #10 Q&A – Dialogs

Posted on:

The 10th and final webinar in our Accessibility Basics Webinar Series covered best practices for accessible dialogs. In this post the presenter – Accessibility Training Specialist Erica Zelmanowicz – has provided answers to the questions we received during the webinar. The webinar slides, transcript, and recorded presentation can be accessed from the Accessibility Basics Series #10 resources page.  Resources from the full series are available on the SSB Webinars page. Dialogs Webinar Q&A If you use role=dialog, do you still need to add offscreen text to demarcate the boundary of dialog? //EZ: role=”dialog” will help identify the grouping of the content as… Read More

Accessibility Basics Series #9 Q&A – ARIA

Posted on:

Last week’s presentation in our Accessibility Basics Webinar Series covered best practices for ARIA. In this post Chief Accessibility Officer Jonathan Avila has provided answers to the questions we received during the webinar. The webinar slides, transcript, and recorded presentation can be accessed from the Accessibility Basics Series #9 resources page.  Resources from the full series to date are available on the SSB Webinars page. ARIA Webinar Q&A When using a UL to contain a list of navigation links, would you recommend adding role=”navigation” to it directly, to a div around it, or not at all? //JA: Use a div with… Read More

Accessibility Basics Series #8 Q&A – Focus Control

Posted on:

Last week’s presentation in our Accessibility Basics Webinar Series covered best practices for Focus Control. Accessibility Training Specialist Erica Zelmanowicz presented the webinar and has provided answers to the questions we received during Q&A – both those that were answered during the webinar and those we weren’t able to get to during the allotted time. The webinar slides, transcript, and recorded presentation can be accessed from the Accessibility Basics Series #8 resources page.  Resources from the full series to date are available on the SSB Webinars page. Focus Control Q&A You mentioned earlier to give a Dialog heading focus when it opens,… Read More

Accessibility Basics Series #7 Q&A – Accessible Forms

Posted on:

Last week’s presentation in our Accessibility Basics Webinar Series covered best practices for Accessible Forms. Senior Director of Client Services Mona Rekhi presented the webinar and has provided answers to the questions we received during Q&A – both those that were answered during the webinar and those we weren’t able to get to during the allotted time. The webinar slides, transcript, and recorded presentation can be accessed from the Accessibility Basics Series #7 resources page.  Resources from the full series to date are available on the SSB Webinars page. Forms Q&A Is there a reason why the * is at the end… Read More

ZIP, Z I P, or Z.I.P.? Forcing Correct Pronunciation in Screen Readers

Posted on:

If you’ve ever used a GPS navigation system or app while on a road trip, you know that sometimes the software can’t parse an abbreviation or pronunciation that we take for granted. For example, St. Dunston Lane gets read as “Street Dunston Lane” or McLean is read as “McLEEN” instead of “McLANE.” These are not life or death issues in terms of vehicle navigation or accessibility, but they can be annoying. What do you do when a screen reader is mispronouncing a word that you consider important to your organization’s message?  In general, we do not recommend screen reader specific… Read More

Accessibility Basics Series Q&A – Data Tables

Posted on:

Last week’s presentation in our Accessibility Basics Webinar Series covered best practices for accessible data tables. Training Director Eric Lyons presented the webinar and has provided answers to the questions we received during Q&A – both those that were answered during the webinar and those we weren’t able to get to during the allotted time. The webinar slides, transcript, and recorded presentation can be accessed at info.ssbbargroup.com/accessibility-basics-series-5_gateway. Would you recommend using the <caption> tag all the time, or if a heading is just above the table is that sufficient? //EL: If a heading is used to section off content that includes the… Read More

Accessibility Basics Series Q&A – Page Structure

Posted on:

Last week’s presentation in our Accessibility Basics Webinar Series covered best practices for page structure. Training Director Eric Lyons presented the webinar and has provided answers to the questions we received during Q&A – both those that were answered during the webinar and those we weren’t able to get to during the allotted time. The webinar slides, transcript, and recorded presentation can be accessed at info.ssbbargroup.com/accessibility-basics-series-4_resources. What is the rule for character limit for the meta title? //EL: 150 characters us the desired limit per the W3C Are page title standards also applicable to pop-up pages? //EL: If you have a new… Read More

Accessibility Basics Series Q&A – Non-text Elements

Posted on:

Last week’s presentation in our Accessibility Basics Webinar Series covered best practices for non-text elements. Training Specialist Erica Zelmanowicz presented the webinar and has provided answers to the questions that came in during Q&A – including those we weren’t able to get to during the allotted time. The webinar slides, transcript, and recorded presentation can be accessed at info.ssbbartgroup.com/accessibility-basics-series-3_resources. Why use the term “non-text elements” instead of images? Erica: Technically the term non-text element refers not just to images but also word art, charts/graphs, and decorative images such as background images.  Non-Text Elements is just a broader term. Is there a… Read More

Accessible Images Using Angular

Posted on:

Angular.js is becoming a widely used framework for web development. The framework allows developers to create readable code, is known to be fully extensible, and works well with other libraries. However, developers must still ensure accessibility when using the angular framework. While angular has accessibility features using the ngAria module, there are basic accessibility techniques that still need to be considered. Unfortunately, the tutorials in the Angularjs.org site lack basic accessibility. For example, the Angular.js tutorial covers two examples using images. The first covers basic images and displaying images on the page. The second takes these images and makes them… Read More

Put yourself on the path to complete accessibility!

Just fill out the form below and we’ll contact you to set up your free consultation with an expert specializing in your industry.

If you need more immediate assistance, please send an email to info@ssbbartgroup.com or call (800) 889-9659. We look forward to helping you!