Blog post archive

• Why doesn’t AI work for producing accessible code?
• Accessibility improvements for user-agents
• Focus Appearance thoughts
• WCAG – Priority of Constituencies
• Overlay comments
• Accessibility auditing and pushing for more
• Sound and Vision quality
• Brexit – letter to my MP
• Oddities in color perception
• Pixels vs Ems commentary
• Firefox zoom preferences
• Is text sizing dead?
• EME Misdirection
• London Accessibility Meetup #6
• EME at the W3C
• The responsive order conflict for keyboard focus
• Units for Media Queries – different conclusion
• Graphics Contrast
• Four levels of accessibility customisation
• AI for Facebook fake-news
• Fixing outlines on click
• ARIA tabs, UI problems and standards
• Get off the Internet
• Laws that undermine security
• Debian upgrade logrotate issue
• Subscription accessibility update
• Zoom for fixed and responsive sites
• ReCAPTCHA updated to no-CAPTCHA
• Flexbox IE11 bugs
• CSUN 2014 round-up
• CSUN: Accessibility in an Agile World
• CSUN: Mobile Testing With the Viking & the Lumberjack
• CSUN: WCAG evaluation methodology
• CSUN: Crowdsourcing the Accessibility Awareness Problem
• CSUN: The anatomy of an accessible app
• CSUN: Accessibility theory vs implementation reality
• CSUN: Browser zoom sucks for low vision users
• CSUN: Authoring Tool Accessibility Guidelines
• CSUN: Unified Accessibility Evaluation Methodology
• CSUN: sitecues
• CSUN: Invisible Visualization: Accessible Information Graphics with Web Tech
• CSUN: Scaling Web Accessibility at Facebook
• CSUN: Responsive design and accessible design
• CSUN: International Association of Accessibility Professionals
• CSUN: Improving accessibility without compromising user experience
• CSUN: WordPress tweetup – accessible presentations
• CSUN 2014 prep
• Use case for high-DPI zoom
• Design bomb in W3C’s garden
• Browser zoom great for accessibility
• UX Bristol 2013
• Peak Appification
• How to hold your iPad
• Screen resolution by ratio
• Text size and screen ratios
• In defence of pixels
• Relative pixels
• Open Rights Group Conference
• Is HDR equivalent to eye exposure?
• Zooming bug in Webkit
• The “Open Web Stack” – Snappy acronym needed
• PDF vs HTML for organisations
• Bristol Council CMS discussion
• Send to my… fridge?
• Are browser-updates a thing of the past?
• HTML5 and WAI-ARIA
• Detecting touch-based browsing
• Removing empty HTML tags from TinyMCE
• SharePoint 2010 Accessibility Event
• Stackoverflow dev day London – Roundup
• ARIAs with Flash, Flex, and AIR
• Techshare Keynote – Richard Schwerdtfeger
• Music industry change
• An unimportant hole in Section 508?
• Usability Introduction – Baltics
• Django – Local vs Live error
• Is accessibility actually usability?
• Window click throughs and scrolling
• Local W3C validator on OSX
• Home links verses logos
• Google Chrome market share
• .net standards champion
• iPods get speech, Apple gets accessible
• dConstruct 2008 notes
• Strange sIFR / screen-reader bug
• Dr Horrible’s sing along blog
• ABBR pattern accessibility
• Nested conditional comments
• Where SEO and accessibility collide
• Adobe open Flash
• Why I don’t buy DRM (music) products
• Galleries in WordPress 2.5
• WCAG Samurai release errata
• Font-based layouts becoming fashionable?
• Email IA for the overloaded
• Voiceover 2 – a WebDev’s guide
• My phone thinks I’m a geek
• Accessibility findings vs recommendations
• Voiceover HTML navigation updates
• Applying a comments policy
• Usability myths and professionals
• If I’m never heard from again…
• CSS – the antithesis of frameworks
• Usability enhancements with JavaScript
• Comparing Tagged PDFs from Office and Acrobat
• Colour Contrast Visualiser – New Tool
• Accessibility kit for Sharepoint
• Office 2007 PDFs – Not (always) accessible
• Responsibility for accessible content
• IA and accessibility
• Testing with a screen reader
• XHTML disrupted by Mobile access
• CMS editable Flash
• @media 2007
• WCAG Samurai published at @media
• Tabindex for keyboard accessibility
• Closing the gap – User Agent improvements
• Note on Non-HTML formats
• Responsibilities in accessibility
• Web mob is the new jury?
• Upcoming relaunched
• Powerpoint bad for your brain?
• Domain woes
• Automated PDF accessibility testing
• SharePoint 2007 accessibility
• .net does accessibility
• Think ahead – Buy accessible
• WYSIWYG editor spec – checklist
• Accessibility vs Universality – implications
• Dissecting CSS Polygons
• Perceptions of page loading speed
• WCAG 2 response on relative units
• WYSIWYG editor spec – preventing problems
• Firefox 3 accessibility
• DRM degrading Windows
• OpenID and trust
• Elastic layout – wrong term?
• Mobile GMail
• WYSIWYG editor spec – interface accessibility
• Reporting on accessibility issues
• Why does google use CAPTCHA?
• Criteria for using Web 2.0
• Depricate the address element?
• WYSIWYG editor spec – layouts
• Anti-spam, hopefully not anti-user
• WYSIWYG editor spec – Tables
• Fund raising for accessibility
• Using label for phishing
• Browser Zoom Comparison
• Raising the bar of mobile browsing
• WYSIWYG editor spec – images
• Internet Apps Roadmap – Questions
• Image replacement and Voiceover
• Accessibility or Help links?
• WYSIWYG editors spec – adding structural code
• Identifying text-only nodes with CSS
• Future of web accessibility
• WYSIWYG editors spec – Importing CSS
• Captions vs subtitles
• WYSIWYG editor spec – allowed HTML
• WYSIWYG editor spec – Overview
• Accessible WYSIWYG editors part 1 – The problem
• Internet Explorer bashing
• Good use of “Web 2.0” technologies
• Why CSS is important for accessibility
• The potential of Voiceover
• Expert usability participants
• WCAG 2 – relative units
• Proprietary software and OS choice
• The four levels of PDF accessibility
• Firefox 2 beta released
• Online passport applications – not ready
• Net neutrality under threat?
• Tesco access updated – and criticised
• CSS tables verses layout tables
• Avoiding spam bounces
• Invalid HTML interfering with accessibility
• Accessible layouts
• Conditional comments in CSS
• Laser eye surgery – an experience
• Subscription accessibility
• Don’t use sp*nsors