Just reading through the schedule for Monday and Tuesday. It's going to be a busy two days.

I know @heydon is presenting. Any one else going?

Spent last night writing an accessible reflowing "show more" list in /#CSS/#JS.

It was an absolute pain, and it only works for elements of the same width.

I think the complication is that I want a single initial row, or multiple rows if my minimum number of elements would overflow, and the explanded list must still render as a single list. Oh, and I want any row to be fully populated. And finally, the list has to render cleanly while JS is loading.

1am finish.

I broke the Permissions by Term module in .

As number of nodes headed towards 100,000 the time to save one new taxonomy term hit 5 f-i-v-e minutes. Wow.

Someone is not efficient.

I found myself disagreeing with tonight. I don't do that often.

"Sighted mouse users (who do not benefit from the [skip to content] link)"

What about magnifier users?
What about head pointer users?
What about ppl on mobile devices who just want to skip banners?

I find those sort of comments a bit frustrating tbh. Personal needs and preferences are more complex than broad brush statements.

My thesis on mobile devices began with a phone call. "Bob! I need a phone! I've got a girlfriend. We're going to text". Only problem was the Paul has advanced MS and this was the late 90s.

MS is a disease of the central nervous system and it affects vision, touch, and kinaesthetics. So a man with no sense of touch, muscle spasms, who can't touch his own nose without serious concentration needed a cell phone...

Even working at Nokia that was a challenge.

It was quite a long road to where I am I guess. Like many people involved in I started down that track through family experience.

I was working at Nokia on UI design methods when my dad became ill with cancer and I gave up full time work to be a carer. Really as a way of getting out of the house I started a master's in multimedia design with a thesis looking at the accessibility of mobile devices.

And that kind of led into the PhD.

Gosh I feel old tonight.

I jjust posted my PhD thesis and hypothesesfrom 17 years ago.

A tad dry.

In plain English, I was looking for a formal, mathematically provable model of accessibility. Or at least something heading in that direction.

I got some blank looks at accessibility conferences, it was just too far outside of people's experience.

There was also a lot of pushback to the idea that people could be reduced to "a f@ algorithm". How the world turns.

Defining accessibility
Pt5

It's okay everyone is safe, I'm not going to post a whole thesis, but if anyone wondered how my mind works, that's a fair example.

I guess it's the thing about accessibility, people come to it from many walks of life. My background is systems analysis and the Shlaer-Mellor method of Object Oriented Analysis and Design. I see the world in patterns and relationships.

Defining accessibility
Pt4

From a thesis long ago in a university far away...

Hypothesis 3

The difference in accessibility between two entities that are expressing the same content, for the same user, and in the same operating context, is measurable and quantitative.

Defining accessibility
Pt3

From a thesis long ago in a university far away...

Hypothesis 2

Specific populations of the relational framework express portable user and device profiles.

Defining accessibility
Pt2

From a thesis long ago in a university far away...

Hypothesis 1

The general case of the encounter between an entity’s capacity to interact and its users physical and cognitive capabilities is capable of expression through a framework of relational models.

Defining accessibility
Pt1

From a thesis long ago in a university far away...

Thesis

Accessibility is the outcome of the encounter between an entity’s capacity to interact and its users physical and cognitive capabilities with capacity, capability, and accessibility all expressed as measurable and quantitative properties.

Robust web navigation
Pt 3

Semantic meaning has also been applied to older elements such as <ul> <ol> and <a>. But it's the new elements that really help. Pressing R repeatedly in will typically move you from header to main menu to breadcrumbs to main content to the footer.

That's really handy when you are living in the sonic design space, which is extremely serial if you don't have an easy way to to gain a level of random access.

And all you need to do as a Dev is use those new elements.

Robust web navigation
Pt 2

The concept of regions/landmarks comes from a -ARIA Recommendation

w3.org/TR/wai-aria-1.1/#landma

The idea is that if we can identify semantic meaning to sections of a web page, assistive tech can can create its own menus to navigate semantically around a page. As a developer you can explicitly do this or...

You can just use the new semantic elements in

Examples are:

<header>
<footer>
<nav>
<main>
<section>
<article>
<aside>

Robust web navigation
Pt 1

I was saying that I failed a site on an a11y audit because it wasn't in and therefore not robust. It's to do with how screen readers provide navigation of a site. On you can press H for the next heading, U for the next unread link on the page, and R for the next region.

It's the region navigation that was missing on the site and that because doesn't support the breadth of semantic markup that the newer HTML5 does.

I failed a payment gateway during an audit last week. It failed on every single principal. Let's focus on Robustness.

The site is built on 1.0 Transitional. Brand new site. Even if the code conforms to XHTML, it's still a fail. We now have that provides semantic elements which properly support assistive tech.

It's like deciding to build a brand new 1986 Ford Fiesta. Cute car, but why do you want a new old car with the safety features of 1986?

Oh, so that's how you do alt text on Mastodon. You tap on the image after it loads and there is a input field within the image.

Not good tool practice guys. It doesn't encourage/remind folks to add alt text when the input field is hidden on load.

Anyway here's me and Squeak with alt text.

Bob, Canadian web developer based in Toronto with a big footprint in digital .

Support and web assets. Mix of development, consulting, and auditing depending on the asset.

CELA is the Centre for Equitable Library Access and provides an online resource of alternative format media

10 years in academia studying for masters and PhD in accessible design methods.

First code: for-loop running on an ICL 2900 mainframe in 1977, aged 13.

Show more
Mastodon for Tech Folks

This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!

We adhere to an adapted version of the TootCat Code of Conduct and follow the Toot Café list of blocked instances. Ash is the admin and is supported by Fuzzface, Brian!, and Daniel Glus as moderators.

Hosting costs are largely covered by our generous supporters on Patreon – thanks for all the help!