Archive
Blog posts in the category: Development
- Bolt-on Accessibility – 5 gears in reverse
- Headings & Accessibility
- Heading off confusion: When do headings fail WCAG?
- Teaching and learning digital accessibility with AIR
- The case for learning sign language as an accessibility engineer
- A TPG Halloween special: the horrors lurking in your HTML
- Captions and Transcripts and Audio Descriptions, Oh My!
- Notes from the a11y underground #2
- Notes from the a11y underground #1
- How do You Test Success Criterion 1.3.5 on Mobile Applications?
- Think like an accessible UX researcher part 3: five common mistakes in usability testing and how to avoid them
- Short note: The abbreviation appreciation society
- Join Us at CSUN 2019!
- Required attribute requirements
- New JAWS Inspect Release
- Short note on scoping mechanisms
- Describing aria-describedby
- Short note on the accessibility of styled form controls
- Shortish note on JAWS support for regions
- Short note on ARIA support
- The current state of modal dialog accessibility
- Short note on progressive ARIA
- Web Content Accessibility Guidelines (WCAG) 2.1
- Short note on getting spaced out with SC 1.4.12 Text Spacing
- Short note on being busy
- TPG at the W3C Web of Things Plugfest, March 2018
- Short note on accommodating the users display preferences on iOS
-
:focus-visibleand backwards compatibility - Colour deficit help
- Short note on what CSS display properties do to table semantics
- Short note on hiding stuff in interactive elements from screen readers
- Accessibility and the Web of Things (WoT) – part 2
- Results from the main landmark survey
- A Tale of Two Rooms: Understanding screen reader navigation
- How “invert brightness” can improve accessibility and help us use our devices
- Short note on making your mark (more accessible)
- Mobile Accessibility Testing Guide for Android and iOS – free
- JAWS wide open
- Cupper: An Inclusive Documentation Builder
- The promise of personalised interfaces
- Short note on labelling text fields in native iOS applications
- Challenges, opportunities and the potential for low-vision access
- Short note on aria-label, aria-labelledby, and aria-describedby
- Shut up JAWS
- Accessibility and the self-organizing team
- Improving access to landmark navigation
- ARIA alert support
- What is an accessible name?
- Accessibility in an Agile lifecycle
- An overview of PDF inaccessibility
- In browser spellchecking
- Accessibility and the Web of Things (WoT)
- TPG at W3C in 2016
- Windows High Contrast Mode: the limited utility of -ms-high-contrast
- A (not so) short note on ARIA to the rescue
- Notes on ZoomText Web Finder
- What does accessibility supported mean?
- Using the HTML lang attribute
- Custom Element Semantics
- The CSUN 2016 UXathon
- Short note on use of alt=”” and the title attribute
- Short note on improving usability of scrollable regions
- The state of hidden content support in 2016
- Simple standalone toggletip widget pattern
- Simple inline error message pattern
- Does SVG text pass WCAG 1.4.5 (Images of Text)?
- Short note on Jaws keyboard layouts
- WCAG 2.0 Parsing Criterion is a PITA
- Thoughts on “Notes from the future of HTML session at TPAC”
- THUS SPOKE HTML
- Notes on use of multiple ARIA role attribute values
- Easy content organisation with HTML5
- #A11Y Slackers
- Short note on aria-labelledby and aria-describedby
- Flipboard – React Canvas Accessibility
- HTML5 canvas sub DOM – updated 29th march 2020
- The Browser Accessibility Tree
- Rough Guide: browsers, operating systems and screen reader support – Updated 23/06/2017
- Web Components punch list
- filing bugs
- Short note on alt in HTML
- Short Note on ARIA, Dragon and Standards
- The HTML5 Document Outline
- Notes on Guidelines For Speech accessible HTML for Dragon NaturallySpeaking
- aViewer intro
- Using the HTML title attribute – updated March 2020
- HTML5 Accessibility Chops: ARIA role=alert browser support
- What’s ‘large text’ in WCAG 2.0 parlance?
- HTML5 Accessibility Chops: hidden and aria-hidden
- HTML5 Accessibility Chops: the alt decision
- HTML5 Accessibility Chops: Just use a (native HTML) button
- HTML5 Accessibility Chops: the placeholder attribute
- Using the HTML title attribute – Updated March 2020
- HTML5: Techniques for providing useful text alternatives
- Making sure hidden frames are hidden
- WAI-ARIA Implementation in JavaScript UI Libraries – updated
- ARIA Role Support in Safari 4.0
- Notes on accessibility of text replacement using HTML5 canvas
- Thinking About HTML 5 canvas Accessibility
- WAI-ARIA role support – How the MAC browsers stack up
- WAI-ARIA role support – How the browsers stack up
- JAWS version 10 with WAI-ARIA live region support!
- Do WAI-ARIA – Google Is!
- A Brave New alt in {HTML5}
- Introduction to WAI ARIA – Gez Lemon
- ARIA Slider, Part 3
- ARIA Slider, Part 2
- ARIA Slider, Part 1
- Making Twitter Tweet – Using the TPG Notifier
- HTML5 and alt: The editors new clothes
- Developer Beware: Using Flash to Detect Screen Readers
- ARIA Toggle Button and Tri-state Checkbox examples
- How JAWS reads text
- IE 8: alt change and longdesc weirdness
- IE 8 beta with WAI ARIA SUPPORT!
- Screen Readers lack emphasis
- The title attribute – what is it good for? (resurrected)
- AJAX and Screen Readers – Content Access Issues
- Using WAI-ARIA Roles and States with the YUI Menu Control
- Providing Context for Ambiguous Link Phrases
- Fieldsets, Legends and Screen Readers