The document discusses accessibility features in HTML5 forms, including:
- Landmark roles that help users navigate forms, like banner, main, navigation etc.
- ARIA roles and properties that make forms more accessible when semantics are unclear
- Live regions that allow updating parts of forms without refreshing the whole page
- New form input types like date, time, email etc. that are more usable for users of assistive technologies
- Attributes like required, pattern, min/max that provide constraints for form values
MORPHEUS is the new optional responsive portal for Sakai 10 that's under active development. It's been rewritten from the ground up to take advantage of the new web technologies. Its goal is to create a better user experience no matter what device you use.
Morpheus is a new user interface born from extensive usability testing at NYU. It builds off the success and stability of Sakai as a platform with a new interface that's modern and future friendly. It's not just a face lift or a redesign but a foundational web system on which new tools, interactions, and designs can be built.
* Responsive design that works on a wide range of devices
* Uses Sass to create a system that's more organized, maintainable, and easy to contribute to
* Easier to customize for your institution
* New templates take advantage of HTML5 for cleaner markup with increased semantic meaning
A new style guide and design pattern library ? a mini 'bootstrap' for Sakai
Find out what the future of Sakai looks like!
A small introduction about WAI-ARIA where I show its 5 rules and 2 related attributes to improve the web accessibilty into the world. Helped by some facts related to the status of Web accessibility.
Talk had at the FrontEnders Ticino monthly meetup in Bellinzona (Switzerland) on the Global Accessibility Awareness Day (official supporter)
ARIA can be used to make web applications accessible to people with disabilities. This presentation gives an overview of ARIA, how it works and some rules to stick to to get things to work properly
Web Accessibility is more than getting colours to match, and knowing when to change from one display layout to another.
Web Accessibility is more than adding "alt" tags to images and "title" tags to links.
Web Accessibility starts with the Semantics on your web page.
This is a talk I put together to show just how much I DON'T know, and how much each of these areas truly is a specialist field
This session covers why you should pay attention to the accessibility of your web site or application and then walks you through how to do it using WAI-ARIA and JavaScript.
MORPHEUS is the new optional responsive portal for Sakai 10 that's under active development. It's been rewritten from the ground up to take advantage of the new web technologies. Its goal is to create a better user experience no matter what device you use.
Morpheus is a new user interface born from extensive usability testing at NYU. It builds off the success and stability of Sakai as a platform with a new interface that's modern and future friendly. It's not just a face lift or a redesign but a foundational web system on which new tools, interactions, and designs can be built.
* Responsive design that works on a wide range of devices
* Uses Sass to create a system that's more organized, maintainable, and easy to contribute to
* Easier to customize for your institution
* New templates take advantage of HTML5 for cleaner markup with increased semantic meaning
A new style guide and design pattern library ? a mini 'bootstrap' for Sakai
Find out what the future of Sakai looks like!
A small introduction about WAI-ARIA where I show its 5 rules and 2 related attributes to improve the web accessibilty into the world. Helped by some facts related to the status of Web accessibility.
Talk had at the FrontEnders Ticino monthly meetup in Bellinzona (Switzerland) on the Global Accessibility Awareness Day (official supporter)
ARIA can be used to make web applications accessible to people with disabilities. This presentation gives an overview of ARIA, how it works and some rules to stick to to get things to work properly
Web Accessibility is more than getting colours to match, and knowing when to change from one display layout to another.
Web Accessibility is more than adding "alt" tags to images and "title" tags to links.
Web Accessibility starts with the Semantics on your web page.
This is a talk I put together to show just how much I DON'T know, and how much each of these areas truly is a specialist field
This session covers why you should pay attention to the accessibility of your web site or application and then walks you through how to do it using WAI-ARIA and JavaScript.
How to use media queries to optimize the same markup for different devices and features.
Get an overview for designing sites for mobile, desktop and even the iPad. Examples include mimicking native appearance and animations with CSS3.
London React April- r3t & a11y : This is for everyone , Shaun Dunne.React London Community
Accessibility is often treated like a 'nice to have' or a feature, but it need not be that way. We're entering an era of custom and reusable web components where we can step away from using only what the browser vendors will give us and create our own encapsulated components to do and act the way we want them too, but we need to take a step back and ensure that our components can live happily on a platform that is accessed by 40% of the worlds population. React loves Accessibility and its not difficult to add, lets have a look how and why
Accessibility on Windows Phone - Windows Phone Meetup at Nokia - 16 October @...Raj Lal
Learn what accessibility means and how to develop your app and web pages to make it more accessible on mobile devices. An accessible app gives maximum reach to your information, functionality and benefits. The four major disabilities that effect user capabilities are visual, hearing, mobility (difficulty in using the mouse) and cognitive disabilities (which are related to learning abilities). Know how to use the latest HTML5 and Accessible technologies to create for mobile devices.
Parallel session on 'An Introduction to WAI-ARIA' given by Dan Jackson, City University at the Institutional Web Management Workshop 2009, University of Essex, 28 - 30 July 2009.
See http://iwmw.ukoln.ac.uk/iwmw2009/sessions/jackson/ and
http://lanyrd.com/2009/iwmw09/srfxk/
What are accessible names and why should you care?Russ Weakley
This presentation will look at accessible names, how they are exposed in the browsers accessibility tree, and their importance to assistive technologies. There will be a deep dive into simple examples, advanced examples using ARIA, and an overview of the W3C's Accessible Name and Description Computation.
Getting to Know Bootstrap for Rapid Web DevelopmentLaurence Svekis ✔
Learn how to add Bootstrap classes to create amazing Bootstrap effects responsive web projects and rapid modern websites
https://www.udemy.com/getting-to-know-bootstrap-for-rapid-web-development/?couponCode=SLIDESHARE
Rich Internet Applications - How to Make them AccessibleDylan Barrell
Making rich internet applications accessible has been made easier through the introduction and support of WAI-ARIA. This presentation provides and introduction to WAI-ARIA and how to successfully use it to make interactive web applications accessible
WAI-ARIA An introduction to Accessible Rich Internet Applications / CSS Minsk...Patrick Lauke
Vanilla HTML is limiting and boring. Our clients demand highly engaging and interactive web experiences. And wouldn’t you know, with just a bit of HTML and JavaScript we can craft amazing custom controls, widgets and effects that go far beyond the confines of traditional static markup. But how can we ensure that these custom experiences are both understandable and usable for people with disabilities, and in particular those using assistive technologies such as screen readers?
In this talk, we will look at the basics of making some common custom-built components accessible - covering how browsers and assistive technologies interact, the limitations of HTML, and how ARIA can help make interactive experiences more accessible. In addition, we will explore some of the recent additions in ARIA 1.1, as well as some particular challenges when it comes to traditional ARIA patterns and assistive technologies on mobile/tablet/touch devices.
Evergreen slidedeck at https://patrickhlauke.github.io/aria/presentation/ / https://github.com/patrickhlauke/aria/
WAI-ARIA An introduction to Accessible Rich Internet Applications / JavaScrip...Patrick Lauke
Vanilla HTML is limiting and boring. Our clients demand highly engaging and interactive web experiences. And wouldn’t you know, with just a bit of HTML and JavaScript we can craft amazing custom controls, widgets and effects that go far beyond the confines of traditional static markup. But how can we ensure that these custom experiences are both understandable and usable for people with disabilities, and in particular those using assistive technologies such as screen readers?
In this talk, we will look at the basics of making some common custom-built components accessible - covering how browsers and assistive technologies interact, the limitations of HTML, and how ARIA can help make interactive experiences more accessible. In addition, we will explore some of the recent additions in ARIA 1.1, as well as some particular challenges when it comes to traditional ARIA patterns and assistive technologies on mobile/tablet/touch devices.
Evergreen slidedeck at https://patrickhlauke.github.io/aria/presentation/ / https://github.com/patrickhlauke/aria/
Presentation by Rich Schwerdtfeger, CTO Accessibility IBM Software,
Steve Faulkner Technical Director, The Paciello Group,
Marco Zehe,Mozilla Corporation discussing progress in the development implementation of accessibility support for HTML5.
Delivering Critical Information and Services [JavaScript & Friends 2021]Aaron Gustafson
Early on, Internet access was considered a luxury. Those times have passed and the Internet, especially the Web, has become a necessity. Whether your users are trying to access their money, gather health information, attend class, apply for assistance, or any of the other hundreds (if not thousands) of critical tasks people do on the web, your site needs to be prepared to meet their needs. And it needs to work, no matter what.
In this session, I discuss the many challenges to delivering critical information and services as well as the steps you can take to overcome those challenges. He’ll explore ways to make sure you can meet users on a variety of devices—and not the just the latest and greatest high end ones folks are talking about; how to make it accessible to people with disabilities; and how to load—and load quickly—on limited- bandwidth connections.
How to use media queries to optimize the same markup for different devices and features.
Get an overview for designing sites for mobile, desktop and even the iPad. Examples include mimicking native appearance and animations with CSS3.
London React April- r3t & a11y : This is for everyone , Shaun Dunne.React London Community
Accessibility is often treated like a 'nice to have' or a feature, but it need not be that way. We're entering an era of custom and reusable web components where we can step away from using only what the browser vendors will give us and create our own encapsulated components to do and act the way we want them too, but we need to take a step back and ensure that our components can live happily on a platform that is accessed by 40% of the worlds population. React loves Accessibility and its not difficult to add, lets have a look how and why
Accessibility on Windows Phone - Windows Phone Meetup at Nokia - 16 October @...Raj Lal
Learn what accessibility means and how to develop your app and web pages to make it more accessible on mobile devices. An accessible app gives maximum reach to your information, functionality and benefits. The four major disabilities that effect user capabilities are visual, hearing, mobility (difficulty in using the mouse) and cognitive disabilities (which are related to learning abilities). Know how to use the latest HTML5 and Accessible technologies to create for mobile devices.
Parallel session on 'An Introduction to WAI-ARIA' given by Dan Jackson, City University at the Institutional Web Management Workshop 2009, University of Essex, 28 - 30 July 2009.
See http://iwmw.ukoln.ac.uk/iwmw2009/sessions/jackson/ and
http://lanyrd.com/2009/iwmw09/srfxk/
What are accessible names and why should you care?Russ Weakley
This presentation will look at accessible names, how they are exposed in the browsers accessibility tree, and their importance to assistive technologies. There will be a deep dive into simple examples, advanced examples using ARIA, and an overview of the W3C's Accessible Name and Description Computation.
Getting to Know Bootstrap for Rapid Web DevelopmentLaurence Svekis ✔
Learn how to add Bootstrap classes to create amazing Bootstrap effects responsive web projects and rapid modern websites
https://www.udemy.com/getting-to-know-bootstrap-for-rapid-web-development/?couponCode=SLIDESHARE
Rich Internet Applications - How to Make them AccessibleDylan Barrell
Making rich internet applications accessible has been made easier through the introduction and support of WAI-ARIA. This presentation provides and introduction to WAI-ARIA and how to successfully use it to make interactive web applications accessible
WAI-ARIA An introduction to Accessible Rich Internet Applications / CSS Minsk...Patrick Lauke
Vanilla HTML is limiting and boring. Our clients demand highly engaging and interactive web experiences. And wouldn’t you know, with just a bit of HTML and JavaScript we can craft amazing custom controls, widgets and effects that go far beyond the confines of traditional static markup. But how can we ensure that these custom experiences are both understandable and usable for people with disabilities, and in particular those using assistive technologies such as screen readers?
In this talk, we will look at the basics of making some common custom-built components accessible - covering how browsers and assistive technologies interact, the limitations of HTML, and how ARIA can help make interactive experiences more accessible. In addition, we will explore some of the recent additions in ARIA 1.1, as well as some particular challenges when it comes to traditional ARIA patterns and assistive technologies on mobile/tablet/touch devices.
Evergreen slidedeck at https://patrickhlauke.github.io/aria/presentation/ / https://github.com/patrickhlauke/aria/
WAI-ARIA An introduction to Accessible Rich Internet Applications / JavaScrip...Patrick Lauke
Vanilla HTML is limiting and boring. Our clients demand highly engaging and interactive web experiences. And wouldn’t you know, with just a bit of HTML and JavaScript we can craft amazing custom controls, widgets and effects that go far beyond the confines of traditional static markup. But how can we ensure that these custom experiences are both understandable and usable for people with disabilities, and in particular those using assistive technologies such as screen readers?
In this talk, we will look at the basics of making some common custom-built components accessible - covering how browsers and assistive technologies interact, the limitations of HTML, and how ARIA can help make interactive experiences more accessible. In addition, we will explore some of the recent additions in ARIA 1.1, as well as some particular challenges when it comes to traditional ARIA patterns and assistive technologies on mobile/tablet/touch devices.
Evergreen slidedeck at https://patrickhlauke.github.io/aria/presentation/ / https://github.com/patrickhlauke/aria/
Presentation by Rich Schwerdtfeger, CTO Accessibility IBM Software,
Steve Faulkner Technical Director, The Paciello Group,
Marco Zehe,Mozilla Corporation discussing progress in the development implementation of accessibility support for HTML5.
Delivering Critical Information and Services [JavaScript & Friends 2021]Aaron Gustafson
Early on, Internet access was considered a luxury. Those times have passed and the Internet, especially the Web, has become a necessity. Whether your users are trying to access their money, gather health information, attend class, apply for assistance, or any of the other hundreds (if not thousands) of critical tasks people do on the web, your site needs to be prepared to meet their needs. And it needs to work, no matter what.
In this session, I discuss the many challenges to delivering critical information and services as well as the steps you can take to overcome those challenges. He’ll explore ways to make sure you can meet users on a variety of devices—and not the just the latest and greatest high end ones folks are talking about; how to make it accessible to people with disabilities; and how to load—and load quickly—on limited- bandwidth connections.
Designing the Conversation [Beyond Tellerrand 2019]Aaron Gustafson
Over time, your users will become more accustomed to and reliant on voice-based interactions with their computers and, thereby, the web. Enabling them to complete critical tasks without a visual user interface will be crucial for the long-term success of your website. In this session, Aaron Gustafson will discuss how smart markup choices can improve the overall usability and accessibility of your projects without disrupting your current workflow.
For the last three years, our industry has been coming to terms with Progressive Web Apps (PWAs) and what they mean for the work we do every day. Scores of articles, reams of documentation, and dozens of white papers touting the successes and failures in this space can really get your head spinning. It’s easy to get lost in the complexities of service workers, manifests, and oh so many JavaScript frameworks and toolkits. Aaron believes it’s time to take a step back and refocus our attention on what really matters: building great web experiences. In this session, you’ll learn how to apply modern web design and development best practices to your web projects. You’ll learn how to grow a project from a core, universally-accessible experience to a sophisticated Progressive Web App that ensures users will be able to access your product, no matter what.
Our industry is abuzz with talk about Progressive Web Apps (PWAs) and with good reason: they are a great way to improve the experiences our users have on our sites, especially when it comes to performance. Using Service Workers—a key component of PWAs—we can manage network requests and the cache to an incredibly granular degree. We can also totally abuse the privilege Service Workers grant us when it comes to writing files to disk.
In this session, Aaron Gustafson will discuss some of the potential pitfalls in implementing Service Workers, especially when it comes to managing heavy files like images and video. He’ll provide guidance on current best practices in cache management. And he’ll offer a few simple recipes you can put to use right away to deliver amazing experiences for your users that respect their data usage and disk space.
Adapting to Reality [Starbucks Lunch & Learn]Aaron Gustafson
After enjoying more than a decade of relative stability in designing for the 'desktop' web, smartphones had to come along and throw a wrench in the works. It seemed that in an instant, everything changed and nothing was certain any more. The truth is, though, nothing was ever certain.
One of the web’s major strengths is its ability to adapt, to travel anywhere and everywhere in service of its users. All those years we were the ones restraining it with our desire to create a single monolithic experience. But experience is not monolithic. Every person is different, and we all bring our unique perspectives, experiences, and capabilities to the table. A one-size-fits-all approach rarely fits anyone well. When we embrace that, our designs, products, and experiences will be all the better for it.
Conversational Semantics for the Web [CascadiaJS 2018]Aaron Gustafson
Over time, your users will become more accustomed to and reliant on voice-based interactions with their computers and, thereby, the web. Enabling them to complete critical tasks without a visual user interface will be crucial for the long-term success of your website. In this session, Aaron Gustafson will discuss how smart markup choices can improve the overall usability and accessibility of your projects without disrupting your current workflow.
Design is problem solving. Each and every day, we are tasked with finding ways to reduce the friction our users experience on the Web. That means streamlining flows, reducing cognitive load, writing more appropriate copy, and (of course) building accessible experience. But experience is about more than just interface. Our users’ experiences begin with their first request to our servers. In this intensely practical session, Aaron will explore the ins and outs of page load performance by showing how he made the web site of the 10K Apart meet its own contest rules, by having a site that was functional and attractive even without JavaScript, and was less than ten kilobytes at initial load. You’ll walk away with a better understanding of the page load process as well as numerous ways you can improve the projects you are working on right now.
PWA: Where Do I Begin? [Microsoft Ignite 2018]Aaron Gustafson
In this session, you'll learn how to apply modern best practices to grow your Progressive Web Apps fluidly from mobile devices all the way to large screen desktop environments. You’ll even learn how to lay the groundwork for reaching users of future form factors and “headless” UIs. We'll focus on design patterns that set you up for success on every device and across platforms and guarantee your users will be able to access your product, no matter what. Additional topics will include a primer on how your PWA can integrate more tightly with Windows 10—including how to distribute your PWA via the Store—and how to incorporate accessibility from the very beginning.
Designing the Conversation [Concatenate 2018]Aaron Gustafson
Over time, your users will become more accustomed to and reliant on voice-based interactions with their computers and, thereby, the web. Enabling them to complete critical tasks without a visual user interface will be crucial for the long-term success of your website.
Designing the Conversation [Accessibility DC 2018]Aaron Gustafson
Over time, your users will become more accustomed to and reliant on voice-based interactions with their computers and, thereby, the web. Enabling them to complete critical tasks without a visual user interface will be crucial for the long-term success of your website.
Design is problem solving. Each and every day, we are tasked with finding ways to reduce the friction our users experience on the Web. That means streamlining flows, reducing cognitive load, and writing more appropriate copy, but user experience goes far beyond the interface. Our users’ experiences begin with their first request to our servers. In this intensely practical session, Aaron will explore the ins and outs of page load performance by showing how he made the web site of the 10K Apart meet its own contest rules, by having a site that was functional and attractive even without JavaScript, and was less than ten kilobytes at initial load. You’ll walk away with a better understanding of the page load process as well as numerous ways you can improve the projects you are working on right now.
We, as an industry, tend to have a pretty myopic view of experience. Those of us who work day-to-day in accessibility probably have a broader perspective than most, but I would argue that even we all fall short now and again when it comes to seeing the Web as others do.
Performance as User Experience [AEA SEA 2018]Aaron Gustafson
Aaron Gustafson
Author, Adaptive Web Design
Performance as User Experience
Design is problem solving. Each and every day, we are tasked with finding ways to reduce the friction our users experience on the Web. That means streamlining flows, reducing cognitive load, and writing more appropriate copy, but user experience goes far beyond the interface. Our users’ experiences begin with their first request to our servers. In this intensely practical session, Aaron will explore the ins and outs of page load performance by showing how he made the web site of the 10K Apart meet its own contest rules, by having a site that was functional and attractive even without JavaScript, and was less than ten kilobytes at initial load. You’ll walk away with a better understanding of the page load process as well as numerous ways you can improve the projects you are working on right now.
Performance as User Experience [An Event Apart Denver 2017]Aaron Gustafson
Design is problem solving. Each and every day, we are tasked with finding ways to reduce the friction our users experience on the Web. That means streamlining flows, reducing cognitive load, and writing more appropriate copy, but user experience goes far beyond the interface. Our users’ experiences begin with their first request to our servers. In this intensely practical session, Aaron will explore the ins and outs of page load performance by showing how he made the web site of the 10K Apart meet its own contest rules, by having a site that was functional and attractive even without JavaScript, and was less than ten kilobytes at initial load. You’ll walk away with a better understanding of the page load process as well as numerous ways you can improve the projects you are working on right now.
Over time, your users will become more accustomed to and interacting with their computers on the web. Enabling them to complete critical tasks without a visual user interface will be crucial for the long-term success of your website.
So how do you design a "headless" UI? That's easy: You design the conversation.
Conversation is at the root of every interaction we have, be it with another human being, a game, or with a website. This session will discuss how to design and implement a web application that will allow you to create a web page that will allow you to create HTML documents.
After enjoying more than a decade of relative stability in designing for the 'desktop' web, smartphones had to come along and throw a wrench in the works. It seemed that in an instant, everything changed and nothing was certain any more. The truth is, though, nothing was ever certain.
One of the web’s major strengths is its ability to adapt, to travel anywhere and everywhere in service of its users. All those years we were the ones restraining it with our desire to create a single monolithic experience. But experience is not monolithic. Every person is different and we all bring our unique perspectives, experiences, and capabilities to the table. A one-size-fits-all approach rarely fits anyone well. When we embrace that, our designs, products, and experiences will be all the better for it.
In this talk, Aaron will discuss and dissect several adaptive interfaces and demonstrate how they smartly morph to meet their users’ needs — slow connections, older browsers, narrow screens, and even no screens at all. He’ll also introduce you to a battle-tested tool for planning, discussing, building and testing adaptive interfaces.
6. Accessibility & Forms
All the site’s a play...
The role attribute
Defines the part an element is playing (assuming it’s different than the
semantics would otherwise imply).
<section id="main" role="main">
<!-- The primary content for the page would go here -->
</section>
17. Accessibility & Forms
Landmark roles
application
A region of the page representing a unique software unit executing a set of tasks for its
users. It is an area where assistive technologies should also return browse navigation
keys back over to the web application in this region.
banner
A region that contains the prime heading or internal title of a page.
complementary
A supporting section of the document that remains meaningful even when separated
from the main content.
contentinfo
Metadata that applies to the parent document.
form
A region of the document that represents a collection of form-associated elements.
main
navigation
search
18. Accessibility & Forms
Landmark roles
main
The main content of a document.
navigation
A collection of navigational elements (usually links) for navigating the document or
related documents.
search
The search tool of a web document.
19. Accessibility & Forms
Structural roles
article
columnheader
definition
directory
document
group
heading
img
list
listitem
math
note
presentation
region
row
rowheader
separator
22. Accessibility & Forms
Structural roles
article
A section of a page that forms an independent part of a document, page, or site.
group
A set of user interface objects which are not intended to be included in a page summary
or table of contents by assistive technologies.
note
A section whose content is parenthetic or ancillary to the main content of the resource.
presentation
An element whose implicit native semantics will not be mapped to the accessibility API.
region
A large perceivable section of a web page or document, that the author feels is
important enough to be included in a page summary or table of contents.
separator
A divider that separates and distinguishes sections of content or groups of menu items.
23. Accessibility & Forms
Semantic comparison
Ad-hoc ARIA Role HTML5
#header, #top banner header (kind of)
#main, #content main none
#extra, .sidebar complementary, note aside
#footer, #bottom contentinfo footer
#nav navigation nav
.hentry article article
26. Accessibility & Forms
Widget roles
<span role="button">OK</span>
(of course <button>OK</button> would be better)
27. Accessibility & Forms
Widget roles
<span role="button">OK</span>
(of course <button>OK</button> would be better)
<div role="alert">
<p>Something went wrong.</p>
</div>
28. Accessibility & Forms
Widget roles
<span role="button">OK</span>
(of course <button>OK</button> would be better)
<div role="alert">
<p>Something went wrong.</p>
</div>
<div role="alertdialog">
<p>Something went wrong.</p>
<img src="x.png" alt="dismiss" role="button" />
</div>
29. Accessibility & Forms
Widget roles
alert marquee slider
alertdialog menuitem spinbutton
button menuitemcheckbox status
checkbox menuitemradio tab
combobox option tabpanel
dialog progressbar textbox
gridcell radio timer
link radiogroup tooltip
log scrollbar treeitem
Widget Container Roles
grid menubar tree
listbox tablist treegrid
menu toolbar
32. Accessibility & Forms
Widget states
B B
(off) (on)
<span>
<img src="bold-off.png" alt="bold" />
</span>
<span>
<img src="bold-on.png" alt="bold" />
</span>
33. Accessibility & Forms
Widget states
B B
(off) (on)
<span>
<img src="bold-off.png" alt="not bold" />
</span>
<span>
<img src="bold-on.png" alt="bold" />
</span>
34. Accessibility & Forms
Widget states
B B
(off) (on)
<span role="button" aria-pressed="false">
<img src="bold-off.png" alt="not bold" />
</span>
<span role="button" aria-pressed="true">
<img src="bold-on.png" alt="bold" />
</span>
35. Accessibility & Forms
Widget states
aria-busy
aria-checked
aria-disabled
aria-expanded
aria-grabbed
aria-hidden
aria-invalid
aria-pressed
aria-selected
aria-valuenow (the W3C defines this as a “property”)
aria-valuetext (ditto)
39. Accessibility & Forms
Live regions
<span id="chars_left_notice" class="numeric">
<strong id="status-field-char-counter"
class="char-counter">140</strong>
</span>
40. Accessibility & Forms
Live regions
<span class="tweet-counter">140
<b class="hidden"> characters remaining</b></span>
.hidden {
position: absolute;
left: −999em;
}
41. Accessibility & Forms
Live regions
<span class="tweet-counter">maximum of 140 characters</span>
<span class="tweet-counter">140
<b class="hidden"> characters remaining</b></span>
42. Accessibility & Forms
Live regions
<span aria-live="polite" aria-atomic="true"
class="tweet-counter">140<b class="hidden">
characters remaining</b></span>
44. Accessibility & Forms
Notification options
off
change not announced
polite
change announced after user completes her current activity
assertive
user agent should interrupt the user’s activity, but not immediately
46. Accessibility & Forms
For more
WAI-ARIA Spec
w3.org/TR/wai-aria/
WAI-ARIA Support in Browsers
paciellogroup.com/blog/aria-tests/ARIA-SafariaOperaIEFF.html
48. Accessibility & Forms
HTML4 best practice
<table summary="Characteristics are given in the second column, with the negative
side in the left column and the positive side in the right column">
<caption>Characteristics with positive and negative sides</caption>
<thead>
<tr>
<th scope="col">Negative</th>
<th scope="col">Characteristic</th>
<th scope="col">Positive</th>
</tr>
</thead>
<tbody>
<tr>
<td>Sad</td>
<th scope="row">Mood</th>
<td>Happy</td>
</tr>
<!-- … -->
</tbody>
</table>
49. Accessibility & Forms
HTML5 options
<p>In the following table, characteristics are given in the second
column, with the negative side in the left column and the positive
side in the right column.</p>
<table>
<caption>Characteristics with positive and negative sides</caption>
<thead>
<tr>
<th scope="col">Negative</th>
<th scope="col">Characteristic</th>
<th scope="col">Positive</th>
</tr>
</thead>
<tbody>
<!-- … -->
</tbody>
</table>
50. Accessibility & Forms
HTML5 options
<table>
<caption>
<strong>Characteristics with positive and negative sides.</strong>
<p>Characteristics are given in the second column, with the
negative side in the left column and the positive side in the right
column.</p>
</caption>
<thead>
<tr>
<th scope="col">Negative</th>
<th scope="col">Characteristic</th>
<th scope="col">Positive</th>
</tr>
</thead>
<tbody>
<!-- … -->
</tbody>
</table>
51. Accessibility & Forms
HTML5 options
<table>
<caption>
<strong>Characteristics with positive and negative sides.</strong>
<details>
<summary>Help</summary>
<p>Characteristics are given in the second column, with the
negative side in the left column and the positive side in the right
column.</p>
</details>
</caption>
<thead>
<tr>
<th scope="col">Negative</th>
<th scope="col">Characteristic</th>
<th scope="col">Positive</th>
</tr>
</thead>
<tbody>
<!-- … -->
</tbody>
</table>
52. Accessibility & Forms
HTML5 options
<figure>
<figcaption>Characteristics with positive and negative sides</figcaption>
<p>Characteristics are given in the second column, with the
negative side in the left column and the positive side in the right
column.</p>
<table>
<thead>
<tr>
<th scope="col">Negative</th>
<th scope="col">Characteristic</th>
<th scope="col">Positive</th>
</tr>
</thead>
<tbody>
<!-- … -->
</tbody>
</table>
</figure>
55. Accessibility & Forms
Dates and times
<input type=”datetime”>
A UI control for selecting a date and time that includes timezone information.
<input type=”datetime-local”>
A UI control for selecting a date and time that does not include timezone information.
<input type=”date”>
A UI control for selecting a date with access to all date components
(day, month and year).
<input type=” month”>
A UI control for selecting a date that provides access to month and year only.
<input type=”time”>
A UI control for selecting a time that does not include timezone information.
<input type=”week”>
A UI control for selecting a date that provides access to week and year only.
57. Accessibility & Forms
Numbers
<input type=”number”>
A UI control for selecting a number.
<input type=”range”>
A UI control for selecting an imprecise number.
59. Accessibility & Forms
New types
<input type=”email”>
A UI control for entering an email.
<input type=”url”>
A UI control for entering a URL.
<input type=”tel”>
A UI control for entering a telephone number.
63. Accessibility & Forms
UI control attributes
autocomplete
Tells the User Agent whether or not the value should be stored.
autofocus
Tells the User Agent to bring focus to the form control on page load.
form
An id reference to the form to which a given control belongs.
required
Indicated the form control must be provided a value.
placeholder
Offers users a short hint about the required value.
64. Accessibility & Forms
Value control
min and max
Lower and upper boundary for an element value (dates, time, and numbers only).
step
The granularity of values allowed (dates, time, and numbers only).
<input type="range" min="1" max="11" step="0.5" .../>
65. Accessibility & Forms
Value control
pattern
A regular expression pattern that the User Agent should validate the input against.
<input type="text"
pattern="d{6}w{3}"
placeholder="6 digits followed by 3 letters"
.../>
66. Accessibility & Forms
Value control
pattern
An id reference to a datalist element containing acceptable values.
<input type="text" list="countries" name="country"/>
<datalist id="countries">
<option>Afghanistan</option>
<option>Åland Islands</option>
<!-- ... -->
</datalist>
67. Accessibility & Forms
Slides available at
http://slideshare.net/AaronGustafson
This presentation is licensed under
Creative Commons
Attribution-Noncommercial-Share Alike 3.0
flickr Photo Credits
“HTML5 logo in Braille” by Ted Drake
“Dual Samsung Monitors” by steve-uk
“Statue of Liberty” by gadl
“Lego” by DavePress
“iFlickr touch screen” by exfordy
“Green Plant” by kevin1024