layout | title | description | categories | |
---|---|---|---|---|
post |
How-to: Future proof your accessibility efforts.
|
Ways to make your accessibility effort as future proof as possible. |
|
layout | title | description | categories | |
---|---|---|---|---|
post |
How-to: Future proof your accessibility efforts.
|
Ways to make your accessibility effort as future proof as possible. |
|
Summary: Use role="application"
very sparingly, if at all.
NEVER use role="application"
on a widely containing element such as <body>
if your page consists mostly of traditional widgets or page elements such as links that the user does not have to interact with in focus mode. Using role="application"
unnecessarily can cause huge headaches for any assistive technology user trying to use your site/application. Only put it on the <body>
element if your page consists solely of a widget or set of widgets that all need the focus mode[^focusmode] to be turned on.
Do Use
- Use if your page has no resemblance to a classic document in roughly over 90% of its content
- Use clear labels within your application
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
struct もじれつ: Printable { | |
let description: String | |
init(string: String) { | |
var mutableString = NSMutableString(string: string) as CFMutableString | |
if CFStringTransform(mutableString, nil, kCFStringTransformLatinHiragana, 0) == 1 { | |
self.description = mutableString as NSString | |
} else { | |
self.description = string | |
} |