Every now and then a developer needs to include special content that should be seen by screen reader users, but not by anyone else. But what is the best way to convey this information? In some cases, an aria-label is the way to go, but more often screen reader-only text is best. Here are some instances for each. Hopefully, this helps answer the question: Should I use aria-label or screen reader-only text?<\/p>\n\n\n\n
The first thing to consider is the content you want to add. If it is essential and\/or beneficial for all users, just make it visible to all users. Screen readers will still see it and so will everyone else, no need to reinvent the wheel.<\/p>\n\n\n\n
That being said, screen reader, only text is great for providing more context to a link whose purpose may be obvious visually due to its location on screen but could be confusing without visual cues (for instance: \u201cAdd to Cart\u201d next to a product on a retail site). Depending on what other contextual clues are nearby, A screen reader user might ask: \u201cAdd what to cart?\u201d<\/p>\n\n\n\n
<a href=\"add-to-cart-link\">Add to Cart<\/a><\/code><\/pre>\n\n\n\nWith some screen reader-only text, you could provide more information that may not be apparent to screen reader users:<\/p>\n\n\n\n
<a href=\"add-to-cart-link\">Add to Cart<span class=\"screen-reader-only\"> super cool product you were considering<\/span><\/a><\/code><\/pre>\n\n\n\nYou can then apply the following CSS rules:<\/p>\n\n\n\n
A quick note about the \u201cclip\u201d CSS rule<\/strong>: clip is deprecated in CSS3 and eventually won\u2019t be supported. Clip-path is replacing clip but until it is widely supported by browsers it is a good idea to include both.<\/p>\n\n\n\n.screen-reader-only {\n position: absolute;\n height: 1px;\n width: 1px;\n clip: rect(1px 1px 1px 1px); \/\/ IE 6 and 7\n clip: rect(1px,1px,1px,1px);\n clip-path: polygon(0px 0px, 0px 0px, 0px 0px);\n -webkit-clip-path: polygon(0px 0px, 0px 0px, 0px 0px);\n overflow: hidden !important;\n}<\/code><\/pre>\n\n\n\nThis will hide the span visually but screen readers will still read it.<\/p>\n\n\n\n
Of course, it should be noted that the previous example could also be accomplished by the use of an aria-label as well by doing:<\/p>\n\n\n\n
<a href=\"add-to-cart-link\" aria-label=\"add product name to cart\">Add to Cart<\/a><\/code><\/pre>\n\n\n\nWhile you could certainly do this, the main upside to using screen reader-only text over an aria-label is that the screen reader is not required to support ARIA, it\u2019s simply reading text on the page that sighted users cannot see. While most screen readers support ARIA, you may not want to rely on it if you don\u2019t have to.<\/p>\n\n\n\n
Another example of when you might want to use screen reader-only text is for headings that were added specifically to help screen reader users. Many screen reader users, when searching for the content they are interested in on a page, will use their screen reader to jump from heading to heading. Unfortunately, it might not always make sense to start each section of the page with a visual heading, so you could instead make those headings screen reader only as a compromise.<\/p>\n\n\n\n
There are a few use cases for aria-label where screen reader-only text won\u2019t suffice. For example, giving your nav tags an aria-label like \u201cMain\u201d or \u201cbreadcrumbs\u201d. This will help differentiate the navigation sections and give the user a better idea of where they are on the page.<\/p>\n\n\n\n
Like this:<\/p>\n\n\n\n
<nav class=\"nav\" aria-label=\"Main\">\n <ul>\n ...\n <\/ul>\n <\/nav>\n \n <nav class=\"nav\" aria-label=\"breadcrumbs\">\n <ul>\n ...\n <\/ul>\n <\/nav>\n\n<\/code><\/pre>\n\n\n\nOr, perhaps you have a page with multiple product listings, and it\u2019s difficult for screen reader users to know where one product ends, and another begins. You might try the following:<\/p>\n\n\n\n
<div role=\"group\" aria-label=\"product\">\n <h4>$50 Gift Card<\/h4>}\n <img src=\"gift-card-image.jpg\" alt=\"$50 gift card\" \/>\n <span class=\"price\">$50.00<\/span>\n <p class=\"description\">A $50 gift card. One size fits all!<\/p>\n <\/div><\/code><\/pre>\n\n\n\nIt should also be noted that the purpose of aria-label is to provide a label for something, typically a control or page section. Say you want to provide different instructions for screen reader users than for sighted users. Here\u2019s the wrong way to do this:<\/p>\n\n\n\n
<div aria-label=\"These are screen reader user specific instructions.\">These are instructions for everyone else.<\/div><\/code><\/pre>\n\n\n\nThe right way to do this:<\/p>\n\n\n\n
<div class=\"screen-reader-only\">These are screen reader user specific instructions.<\/div><\/code><\/pre>\n\n\n\n<div aria-hidden=\"true\">These are instructions for everyone else.<\/div><\/code><\/pre>\n\n\n\nNot only is the second technique more in keeping with the purpose of the aria-label attribute, but it\u2019s also the only one likely to work in most screen readers. In the first example, most screen readers will ignore the aria-label completely.<\/p>\n\n\n\n
As you can see, we often recommend screen reader only text over aria-labels, but both techniques have their drawbacks:<\/p>\n\n\n\n
\n- It\u2019s harder to test; one must use a screen reader to fully test how effective the text is.<\/li>\n\n\n\n
- Since the text does not appear on the page, it runs the risk of being forgotten about, or the element it applies to could get moved or changed, rendering the text useless, outdated, or confusing.<\/li>\n\n\n\n
- It\u2019s not available to everyone; non-screen reader users are excluded from accessing this information, even if it might be of help to them.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"
Every now and then a developer needs to include special content that should be seen by screen reader users, but not by anyone else. But what is the best way […]<\/p>\n","protected":false},"author":11,"featured_media":85471,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[14],"tags":[],"class_list":["post-85469","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog"],"acf":[],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t