I don't post here anymore. Connect with me on:.BlueSky: LinkedIn:

I give up. I quit. Twitter is awful. These are some places I remain active, if you want to connect. LinkedIn:. Mastodon:. Bluesky:.

RT @KaraKane_kk: A bold new look for the homepage 👀.

RT @DWPDigitalJobs: 🆕 We've got an exciting apprenticeship opportunity!. Embark on a career as an Accessibility Specialist and help ensure….

Great article on @webaxe about the #accessibility of strike through formatted text:

If you back something on @Kickstarter and when it finally arrives it’s broken, what options do you have? I’ve reached out to the creator and did everything they asked, sending videos of it not working etc, and now they’re just ignoring me 😅 #Kickstarter.

A photo I took of the Red Footed Falcon that recently visited Northumberland. Alt: Small bird of prey with a speckled underside and dark wings, with a short sharp beak and black mask. It’s on a rock amongst dry grass against a clear sky, sideways on looking over its shoulder.

I think I just found the exact moment I got into accessibility. A tweet in January 2016, after a talk by @dugboticus at GDS in Holborn. Man do you have a lot to answer for. 😆.

Hey @accessibleweb, on this GOVUK Guidance it mentions both @GDSTeam and CDDO in the monitoring section. It’s not clear who is the monitoring and reporting body anymore. Has there there been a reshuffle of responsibility? Or is it a typo?

I've just pushed version 1.5.0 of WCAGify and it has been updated to use WCAG 2.2. #a11y #accessibility #wcag.

Yesterday we got #WCAG 2.2 and 9 new criteria. Under the Public Sector Bodies #Accessibility Regulations, you need to work to the latest version to be compliant, so I've written a blog post on what #WCAG22 might mean for you!. #a11y .

Woohoo! Finally, we have WCAG 2.2. Grace period for transition will likely start from today, with monitoring and reporting against UK Public Sector Bodies kicking in from October 2024.

I was a super early backer on the RollingSquare #AirCard. They didn’t send it out for some reason, then after lots of back and fourth and lots more waiting it finally arrived a year later, and it won’t turn on. My advice, stick to official air tags 😅 this is a piece of junk.

Genuinely heartbroken. 💔.

My final thoughts on #ChatGPT as an accessibility testing tool, is that it's not very good. It's better at helping you to write code than to find problems later. It's primary feature is to parse text, so if your test cases contain clues it will look better than it actually is.

#ChatGPT is better at short technical questions. For example, "How can I make the following button accessible" followed by a small amount of code. It is less reliable when asked to do reports on large amounts of content, where it tends to default back to writing general guidance.

#ChatGPT cannot parse huge amounts of HTML, which makes it a pain as an accessibility tool. You have to paste in chunks. You can do several pastes stating "remember this as HTML" followed by "add this to HTML" which will combine multiple pastes into a variable to query later.

#ChatGPT produces a lot of noise and false positives. It will default to just telling you general best practice, rather than being specific about the code you paste in. For example: "The HTML does not contain images, but if any are added, remember the alt attributes.".

#ChatGPT cannot actually render content, and it cannot access linked files. So it will not find accessibility issues in the CSS if it is not available in <style> tags you paste in. When it has access to CSS, it can find more issues, like ordering using floats and contrast issues.

#ChatGPT makes punts based on class names. If you use the class name '.small-text-with-contrast-issues' then it will likely find the issues. But if you named it '.test-text-1' then it doesn't find it. So remove any clues as to what it is you're trying to test!.