CTO, Opera Software • BS8878 committee member • name in HTML5 spec! • Co-author “Introducing HTML5”, “Web Accessibility: Web Standards and Regulatory Compliance”
condition to bridge the gaps in the socioeconomic inclusion of persons with disabilities. A supportive ecosystem is needed to drive the implementation of accessible digital technologies.” - “Digital Dividends” - World Bank (2016)
to identify features for user interaction, how they relate to each other, and their current state. WAI-ARIA describes new navigation techniques to mark regions and common Web structures as menus, primary content, secondary content, banner information, and other types of Web structures.
The site must be designed around user needs, not organisational structure or operational convenience. • Wherever possible, users should be consulted in formal user- testing. (Those of us within the organisation rarely have the same needs or expectations, and are therefore rarely reliable proxies.) • All content on the site must be accessible to people with disabilities. Where this clashes with aesthetics or organisational convenience, it trumps them. http://www.brucelawson.co.uk/2006/constitution-of-a-new-website/
design is subjective. Where internal stakeholders cannot agree, user-testing should take place. • In both design and content, simplicity beats complexity, increasing the range of devices that can be used to access the Site (including old machines and mobile browsers). Therefore, any proposed technological bells and whistles must have a demonstrable value to visitors.
users with disabilities. Access by everyone regardless of ability is essential. This does not mean that features should be omitted entirely if not all users can make full use of them, but alternate mechanisms should be provided. HTML Design Principles - https://www.w3.org/TR/html-design-principles/
web platform APIs that allow you to create new custom, reusable, encapsulated HTML tags to use in web pages and web apps. Custom components and widgets build on the Web Component standards, will work across modern browsers, and can be used with any JavaScript library or framework that works with HTML. https://www.webcomponents.org/introduction
... would automatically inherit the semantics and behaviour of the button element, with no need to implement these behaviours manually. In general, for any elements with nontrivial behaviour and semantics that build on top of existing elements of HTML, customized built-in elements will be easier to develop, maintain, and consume.”
repeatedly objected to having is=, and in fact, stated publicly that we won't implement this feature” - Ryosuke Niwa https://github.com/w3c/webcomponents/issues/509#issuecomment-224212371
should not be tied to one vendor, and should be free of charge to the user. The code that runs the website must conform to the rules of the various languages used.” • TAKE HOME: respect the tools (HTML, CSS, JS)
up-to-date browsers and decent AT. • With evergreen browsers, this is easier than ever before. Lots of free screenreaders eg VoiceOver, Talkback, NVDA. • If you come to my site with IE6 and an old version of JAWS, don’t tell me that it’s inaccessible.
brucel
nullpo_head
oniak3ibm
marchin1989
naoki_0531
shujisado
duelist2020jp
bengo4com
bigmuramura
chanyou0311
righttouch
bgpat
murashotaro
dougneiner
smashingmag
addyosmani
3n
matthewcrist
bkeepers
samlambert
lara
skipperchong
tammyeverts
