Summary
Digital accessibility is about more than a pass-or-fail label. In this episode of Accessibility Breakdown, Mark Miller and Justin Stockton explore YouTube Playables accessibility tags, ADA website accessibility lawsuits targeting dental practices, and GitHub accessibility statements. They discuss how clearer information about accessibility features and limitations can help people choose games, evaluate software, and understand where improvement is still needed.
The conversation connects accessible gaming, dental website access, and open-source development through a shared theme: transparency and continuous improvement. Mark and Justin examine barriers in online patient forms and PDFs, discuss the legal questions raised by website accessibility litigation, and explain why project-specific accessibility statements matter. They also weigh automated testing against manual audits and user testing, using a component-library example to show how unresolved accessibility issues can become accessibility debt.
Subscribe to the podcast
In this episode
New accessibility tags come to YouTube Playables
By Dara Monasch
- Mark and Justin explore how tags associated with the Accessible Games Initiative communicate accessibility features in YouTube Playables.
- They distinguish identifying supported features from claiming a game is fully accessible: tags help players understand what may work for their needs.
- Consistent accessibility information can help players find suitable games without testing every similar option themselves.
- The hosts see YouTube’s participation as leadership by example and a way to encourage broader adoption of accessibility transparency.
- They challenge the idea that accessibility is binary, emphasizing ongoing improvement and honest communication about limitations.
ADA Website Accessibility Lawsuits Target Dental Practices
- The hosts discuss website accessibility litigation reaching dental practices and why digital access deserves attention alongside physical access.
- Online intake forms and PDFs illustrate how accessibility barriers could affect a prospective patient’s initial interaction with a practice.
- They explore New York litigation and questions about standing and intent to use a business’s services, while noting they are accessibility professionals, not lawyers.
- The conversation raises questions about how ADA Title III, HHS Section 504, and WCAG relate to healthcare accessibility; it is a discussion, not legal advice or a verified compliance timetable.
- Mark and Justin emphasize communicating across legal, leadership, and development teams to move accessibility work forward.
Accessibility statements now have a home on GitHub
By Jan Maarten
- Justin describes how an accessibility statement in a project’s accessibility.md file can make accessibility information more visible alongside other repository documentation.
- The hosts favor project-specific statements that explain completed work, known limitations, and areas for improvement rather than a one-size-fits-all declaration.
- Clear statements help contributors and developers understand a project’s accessibility status before adopting or building on its code.
- Mark and Justin connect this transparency to shift-left accessibility: considering and testing accessibility earlier in development.
- They discuss automated checks as one testing layer, not a replacement for manual audits or testing with people.
- A component-library example illustrates accessibility debt: fixing issues later can require breaking changes and updates across projects that depend on the library.
Mark Miller (00:04)
Hey, welcome to the Accessibility Breakdown. I am Mark, and this is
Justin Stockton (00:08)
Justin?
Mark Miller (00:09)
every week we pay tribute to those who stand out to us as leading by accessibility by picking three topics that strike us in some way. This week, we’re gonna talk about New accessibility tags come to YouTube Playables. This is um an article uh by Dara uh help me out, Justin Monasch.
Justin Stockton (00:33)
You
Mark Miller (00:36)
It’s the last letters I can’t get. uh
Justin Stockton (00:38)
with.
Monash? I’m gonna go with Monash.
Mark Miller (00:40)
Monasch, monish, monash.
Yep. Sorry, Dara. Um the and this is interesting because this is uh YouTube making games more accessible and one, I didn’t know there’s YouTube uh games, but uh now we do. And this has a sort of larger implications than that. the next one will be ADA website
ADA Accessibility Lawsuits Target Dental Practices.
and this is by Rivkin Radler who is uh a uh a lawyer. Um and uh it’s interesting. This is more title three lawsuit stuff, but it’s kind of interesting the way that this is still moving through different sectors. So we’ll talk a little bit about that and we’ll talk about some some other things surrounding that. And then uh uh Accessibility statements now have a home on GitHub by Jan.
Maarten Um
Justin Stockton (01:41)
I’m gonna go with Jan.
Mark Miller (01:42)
Jan Jan Maarten Thank you.
Justin Stockton (01:45)
Given the last name,
I’m gonna go with Jan.
Mark Miller (01:47)
Okay. You’re probably correct.
Justin Stockton (01:47)
But happy to be,
yeah.
Mark Miller (01:50)
Well, it’s interesting
because the last name is spelt with two A’s in a row, A R T N.
Justin Stockton (01:55)
Mm-hmm.
Mark Miller (01:55)
So I don’t know if that’s the clue you’re going with there. Um
Justin Stockton (01:58)
That’s the clue.
Mark Miller (02:00)
But anyways, so let’s let’s start with the the first one here. New accessibility tags come to YouTube Playables and I don’t d were you aware that YouTube had games? Okay. Yeah it
Justin Stockton (02:15)
I was like,
playable? For like, Twitch streams?
Mark Miller (02:19)
What’s that? Yeah.
Justin Stockton (02:21)
Like, what is it? Yeah.
Mark Miller (02:23)
Well, and the interesting thing to me is that YouTube has these these little Playables and they’re kinda like look like sort of cute little games, right? We’re not talking about like, you know, God of War or Call of Duty or anything like that. We’re we’re more in the the the Tetris uh what’s it uh bejeweled,
Justin Stockton (02:40)
The Jeweled. Yeah.
Mark Miller (02:42)
yeah, that that sort of uh that sort of realm. Um but they uh have gone through the trouble of of of tagging these for
accessibility and the cool thing about it is that uh they the the reason why they’re tagging them is because they’re part of the accessible game initiative and the accessible games the I’m sorry, I’m gonna say it again, the accessible games plural initiative. And um the accessible games initiative actually sort of um gives a
I don’t know what you would call it, like a schema for these tags. It’s one of the things that they say if you’re making an accessible game. So they give guidance on how to make an accessible game. And these tags are uh part of that. So it’s good on YouTube for being part of the initiative, for going through the trouble of making their games accessible, right? And to me, this is a bit of a leadership by example, right? Like
YouTube games being accessible is not necessarily going to change the world, but it is such a I don’t even think the popular is the right word for it, but the YouTube platform is just a part of everybody’s life, right? If you’re like I need to look up something that’s video related, YouTube is where you go, right? Whether it’s a clip from a show that you like or a how to video or whatever, it’s just where we automatically go.
And the fact that they’re taking this initiative to make sure that their games are accessible, I think really is uh great leadership.
Justin Stockton (04:28)
I think they’re, well wait, are they making their games accessible or are they just supporting the tagging that says whether or not the game is accessible?
Mark Miller (04:37)
I’m sorry. That’s the way to that’s the way to say it is they’re supporting the tag and this is whether or not the game is accessible. Which is gonna relate a little bit when we get down to the um Accessibility statements now have a home on GitHub that
It’s I think it’s an important concept that when you say something’s accessible, it probably is not one hundred percent accessible, no matter what. Right. Just like if you say, this is bug free, or there’s no I don’t know, there’s no bugs in this, right? It probably doesn’t mean there’s no bugs in that. It means yeah, they’re gonna be hard to find. And yes, there could be a bug because there could be something that nobody even knows has found yet that’s a bug out there, right? You can’t you can’t say what you don’t know.
And even though you’ve looked hard for bugs, there could be one out there. So I think accessibility is at the very least the same thing. But the importance of trying to make something accessible and communicating how far you’ve gotten with that. I think that that’s really where those tags specifically become important. So my impression was is that they’re that they are making an attempt to make the games as accessible as possible and they’re using the tags to
as a means of communication. But maybe it’s that’s wrong.
Justin Stockton (05:54)
Well, I think it’s also, mean, we talked about this a couple of weeks ago, like it’s one of those ways of differentiating your product from someone else’s of being able to say, there are, I mean, if there’s one game that allows you to throw a little ball up onto the screen that pops other balls, there’s a thousand of them. And if you can, and if you’re predicting, if the one that you built is more accessible and you were able to present that in a way that is consistent.
and allows people to search on it to find it, then people that want accessible games or need accessible games are going to be able to find it rather than having to go through all 1,000 of them and determine, yeah, there’s
Mark Miller (06:33)
Mm-hmm.
Justin Stockton (06:34)
nothing here that I can play.
Mark Miller (06:35)
Yeah. And and you’re just being a good steward by saying this is the degree to which we’ve made it accessible. So if there’s something that the developers weren’t able to accomplish or haven’t gotten to yet because it’s more complex than something else, it’s very clear where where you are in that so that you can you can um make proper decisions. You know, this one’s for me, this one’s not for me, kind of thing.
Justin Stockton (07:02)
Yeah, I hope it takes off because Apple did something similar to this with the App Store a couple years
Mark Miller (07:08)
Mm-hmm.
Justin Stockton (07:09)
ago. A couple years ago could have been 10 years ago. I don’t know, but where there’s if you scroll down a little bit, there’s a accessibility kind of report card that tells
Mark Miller (07:18)
Mm-hmm.
Justin Stockton (07:19)
you whether or not an app is accessible. Of all the apps that I’ve ever installed, I don’t think I’ve ever seen one that has it filled out. Maybe I’m just not.
Mark Miller (07:28)
that’s interesting.
Justin Stockton (07:30)
Maybe I’m not used.
I’m not doing it.
Mark Miller (07:32)
But that’s where the that’s
where I go with the leadership by example here is that
Justin Stockton (07:35)
Yeah
Mark Miller (07:36)
YouTube’s going through the trouble. That’s what I’m that’s what I’m saying. They’re going through the trouble of trying to make things accessible as possible.
Justin Stockton (07:42)
Yes.
Mark Miller (07:42)
They’re giving the real admission that like this is an ongoing and takes time and all you know, all of the above, but we’re going to also communicate with you. And that’s I think
Justin Stockton (07:55)
Mm-hmm.
Mark Miller (07:56)
that’s the next step for the world because there’s people out there that still think that accessibility is binary.
And it’s that’s not a dig on anybody. That’s just, you know, people who don’t understand or aren’t exposed to accessibility in the way we are think like, you know, it’s a pass fail, right? You’ve got all these regulations, got you’ve got Title II, you’ve got HHS, you’ve got Title III of the ADE, all this stuff, and uh we’re supposed to be accessible past fail, right? And it’s not the case. That’s why VPATs exist. VPATs say this is how successful you’ve been.
And it’s ongoing. Wherever you are today is not going to be the same place you are tomorrow. So all this stuff has to continue. And we know this, and probably a lot of our audience knows this. Um, but I think that these are just small and maybe not so small because it’s YouTube voices, but it’s YouTube Playables, right? It’s it’s not like so, but I think that sometimes those are the most important lead lead by example.
scenarios is when these smaller like we’re doing this just because we should be doing it, it puts other people kind of on on notice. It brings awareness. I don’t know. I just really like it. I’m really I’m happy and I’m happy
Justin Stockton (09:10)
it.
Mark Miller (09:12)
somebody like YouTube is doing it. You know, it’s not some boutique thing that is just like we’re gonna be accessible. It’s YouTube, you know? They they’re already popular.
Justin Stockton (09:19)
Do you think
YouTube Playables has put LinkedIn on notice for all those little games and things that you can play on LinkedIn? is LinkedIn gonna have to come up with?
Mark Miller (09:28)
my gosh. I just
I accidentally clicked on one of those. I think it was today or yesterday. And I was like, it was like I I don’t know. It was like I opened the wrong door in a like looking for the bathroom or something. I was like, sorry. Like I couldn’t shut it and get out quick enough. Because I why I understand that on YouTube. I understand that maybe on Facebook. I don’t know that I understand the games on LinkedIn. It doesn’t
seem on brand for something that’s primarily supposed to be a business. I just don’t get it. Maybe it’s just me. But if they’re
Justin Stockton (10:05)
Yeah, I don’t know.
Mark Miller (10:06)
gonna do it, let’s tag Let’s tag LinkedIn.
Justin Stockton (10:10)
right.
Mark Miller (10:11)
All right.
Any other comments on this?
Justin Stockton (10:14)
uh No, I think that’s good.
Mark Miller (10:16)
Okay.
Yeah. Yeah. All right. Good good on YouTube. All right. The next one I want to talk about is ADA Website Accessible Lawsuits Target Dental Practices. And this is gonna sound a little bit like a broken record, but I think there’s some stuff to talk about here. So this isn’t yeah,
Justin Stockton (10:33)
Stop me if you’ve heard this one before.
Mark Miller (10:36)
stop me if you’ve heard this exactly, right? So this is by um this is by a law firm called Rivikan Rattler. Um
And they’re uh it a lot of this article is about um um
Is about uh Title III right? Um uh places of public accommodation. So Title III of the ADA, if you break it down, not a lawyer, right? But if you break it down, it basically says places of public accommodation, so places that the public accesses, and that could be a business, that could be the public library, um, a bank, whatever, right? Need to be accessible to people with disabilities. And this uh extends to
The web as a place of public accommodation. So if you’re a bank and you’re letting people you know, you gotta let people get in your building, you gotta let people get on your website. Um um
So that is that’s what they that’s what they point out here. And the interesting thing is is that these lawsuits keep moving from industry to industry to industry. We’re talking about more of a serial plaintiff here, people who are or looking to find places, you know, for lawsuits. And the other interesting thing, and you’re seeing this more and more, is they really double down on the fact that New York State
is a particular area where um there may be difficulties in standing from a federal standpoint, and all sorts of other things that sometimes these things are concentrated in New York where there’s a pretty good precedent um and where the laws are really uh specific around around this. So it’s not going away, right? We’ve got everybody’s focused on Title II and HHS right now.
HHS is is Section 504. But it’s not this this title three stuff just is it it it is continuing to accelerate and this is ten fifteen years later.
Yeah. Um now the interesting thing I found about this is it didn’t mention HHS at all, and I know I’ve jumped into that a couple of times in this. So let me just take a step back and explain what that is. That is the Section 504 of Health and Human Services where they recently put out a ruling recently, year a few years back, right? This is in line with if you’re familiar with the Title Two rule, like these two things kind of
had been running alongside of each other. So Title II was extended in um last year and so was HHS. So HHS’s deadline is in April, if I’m not confusing those deadlines of 2027. And it references WIC it references WCAG 2.1 at the double A level. So these guys talk about how WCAG’s not specifically referenced in the ADA. That is true for Title III of the ADA.
It is referenced in Title II of the ADA, which does not apply.
Not a lawyer, does not apply to health related entities. But very similar ruling under the health and human services does apply to health related entities. I am pretty sure that includes dental offices. So um there’s actually probably and again, I’m not a lawyer, so our we’re we’re accessibility experts, we’re not
People who interpret the law. Um, but we’re exposed to this stuff. So that is how I’m seeing this as a as a uh accessibility professional. Um so there may be even more here that that people need to be concerned with. But these guys uh seem to know what they’re talking about just based on this article, and uh are obviously seeing these these lawsuits creep up still.
Justin Stockton (14:34)
Yeah,
yeah, that’s another case where like it was particularly like that New York there’s that Calhoun versus Swarovski Swarovski crystal people.
Mark Miller (14:39)
Mm-hmm. Mm-hmm. Yep. That’s that’s uh
Justin Stockton (14:45)
And ah that’s an that’s like every time I see it mentioned, I’m like, wait, I know that one. Like, that’s
Mark Miller (14:51)
Mm-hmm.
Justin Stockton (14:51)
a really interesting case, because that one says that you have to ah you can’t just do like the drive by litigation, like you actually haven’t have to have an intent.
purchase or return to that place again.
Mark Miller (15:05)
Mm-hmm.
Justin Stockton (15:07)
So for like a dentist office, it would apply, you know, ah but unless you are, what if you were blocked from actually filling out the forms or the PDFs or things like that for that initial visit, for that, you know, that initial cleaning uh
Mark Miller (15:21)
Mm-hmm.
Justin Stockton (15:23)
or checkup. So would you not have an intent to come again? Like that’s a weird kind of place, like how I want to
I’ll be curious to see if at some point down the line, if that doesn’t get challenged by someplace like a dentist office where there’s that
Mark Miller (15:39)
Mm-hmm.
Justin Stockton (15:40)
typically that initial meeting ah where you determine whether or not you want to go forward with additional services and does Calcano apply.
Mark Miller (15:49)
Yeah, I what Calcano did was um
increase the threshold for standing. So standing I and again, I’m not a lawyer, so let me try to do my best here. But the way I understand standing is it’s is it’s it’s exactly that. Like if I’m in Hawaii and I want to sue a company in New York because um I’m in a wheelchair and we’ll use a we’ll it could be for anything, right? But we’ll use a accessibility and um they don’t have a ramp. They only have stairs. Well I don’t have standing because there’s
No way I would have been trying to get unless I went on uh visited New York, but let’s say that didn’t happen. You you actually have to be somebody who could have you know, gone into the building, right? You can’t you can’t be somebody that lives in Hawaii and has never been to New York. So um that kind of standing I think really helps tamp down just random lawsuits that people are just throwing out there to see if they stick a little bit.
And um the Calcano tightened the threshold uh for standing, you know. So that’s that’s that whole if you just for if people if you’re in this business and you kind of hear that standing, because I know I heard it in the beginning quite a bit and I was like, wait a minute, what’s it? I had to go look it up, you know. But that’s what it that’s what it refers to. So it’s really interesting. It’s really interesting to see how these things um play out. And it’s interesting to see that it’s specifically sort of landing in the dental offices now.
Okay. Well that’s a good case to be familiar with if you’re not familiar with it.
Justin Stockton (17:26)
There’s some, it is really funny how like in accessibility, not only do you have to know like your WCAG guidelines and like how to audit things and look at things and then on the web, but then there’s PDFs and mobile and then you need a little, little, little bit of development. you need to learn some, some legal jargon so that you understand how
Mark Miller (17:42)
Mm-hmm.
Justin Stockton (17:43)
to read the laws that are dictating whether or not you’re supposed to, like it just, it just grows and grows and grows and grows and grows and grows and grows. So.
Mark Miller (17:53)
It does, it does, and it helps because accessibility’s you know, it’s not a simple thing and it’s often influenced by multiple stakeholders. So as a professional, regardless of what your role is, if you’re if it’s similar to ours or if you’re working in an organization, um, as the accessibility coordinator or whatever, you know, whatever it might be called.
your ability to effectively communicate with all those different rules is directly related to your ability to successfully move accessibility forward. That’s a big piece of it, right? Can you communicate to leadership? Can you communicate with counsel effectively? Like do you kind of, you know, can you can you sort of hold your own in all these different rooms? And the more and more that you can do that, um, the more and more
success you’ll have in in moving it. That’s why you know, I I worked with a woman named um Jaunita uh at a large credit union for a long time and she uh was a lawyer and she was the accessibility professional and she understood business and she was incredibly successful at moving the needle within the organization because she could hang tight
really tight in all the different rooms with all the different influencers. Um, and it was uh amazing to watch what she accomplished over the years. Um, and to this day, that credit union has some of the best vendor management programs, um, you know, accessibility. Uh she stood up accessibility mentorship programs with the developers. She also could code like just all of it, you know.
Okay, great. Um I say could, she still can. She’s just not with that organization anymore. I’m like gotta check my use of the past tense here. Make sure it’s
not confusing people. All right, so the
Let’s jump into this last one here and why don’t you set it up because this is Accessibility statements now have a home on GitHub and you’re much more of a GitHub guy than I am. I always feel like I always get like the imposter syndrome when I’m in GitHub because I’m not like I’m not like a
Justin Stockton (20:06)
you
Mark Miller (20:06)
developer, you know, but I have to go in there for all sorts of reasons and do stuff and I can kind of you know, I’m not ignorant of code. But uh you, on the other hand, are have been around for a long time.
and doing development work for a long time and you probably remember you probably were in GitHub. My guess is you were in GitHub the day it launched. Oh, come on.
Justin Stockton (20:30)
No. But
now you made me wonder to go and look and see how long I have been.
Mark Miller (20:34)
When did it launch?
You you set this up, I’ll look up when GitHub launched. I knew that that was gonna that was gonna make you wanna do that.
Justin Stockton (20:40)
Oh
Mark Miller (20:42)
I’m gonna look it up in real time right here. Live. Live lookup of GitHub.
Justin Stockton (20:47)
where does it tell you? It’s gotta tell you where.
Mark Miller (20:49)
No, I’m gonna look that up. You set up the article. Yeah.
Justin Stockton (20:52)
OK, no, I was
looking up when I actually joined GitHub.
Mark Miller (20:55)
when you joined
GitHub. I was gonna look up when GitHub launched.
Justin Stockton (20:59)
Gotcha. uh GitHub recently announced, think, part of accessibility universe, GitHub universe, ah they announced that ah they are now going to feature uh accessibility statements that have been defined in a special accessibility.md. that’s mark, MD stands for markdown. ah That if you write up
one of these files that includes basically an accessibility statement for your project, this statement will now have a prominent position within the About Us or the About Projects section of the project, along with things like your ReadMe, your Code of Conduct, contributing guidelines, all those things. So accessibility, if you do include one of these files, it’s gonna be featured prominently there, which
Mark Miller (21:55)
Mm.
Justin Stockton (21:55)
is huge. ah
And so this gives us a way to very quickly see which projects have accessibility statements, which ones don’t, what those statements are, quickly linking to them. It provides more visibility to accessibility statements within GitHub and across all the various projects because they also have a uh toolkit made available that will actually help you kind of draft that initial
uh statement. it’s pretty cool. It’s nice to see uh accessibility becoming a first class citizen in open source projects.
Mark Miller (22:39)
Yeah. So before I dive in, February twenty uh two thousand eight was when GitHub started and
I think this is another great lead by example.
Justin Stockton (22:48)
Mm-hmm.
Mark Miller (22:48)
Where GitHub
is is i you know
making accessibility one of the priorities within everything that open source development is about. And it’s really interesting to read through the article because it talks a lot about how to fill out the statement and it makes a couple of interesting points that I think
you know, or or are good general points t for people to think about. And one of them is that
There’s no there’s no it’s not formulaic and it’s not a form that you fill out. It’s very open-ended with a lot of guidance, right? And part of the reason they say that it’s that way is because what your application needs to say about accessibility may be very different than what my application needs to say about accessibility. That this this idea of sort of one size fits all is not is not great, and that
Again, the idea is not to be accessible, but it’s to tell other people that might come in and pick up on your project how far you’ve gotten. What have you done? Where are you with this? Right. And I think it also starts to hint at this shift-left idea. This idea that it may not be perfect, but we’ve tried to do some stuff early on around accessibility. And here’s where we’ve arrived.
Right. So it’s it’s in a way it’s it’s again it’s communicative, right? It’s communicating what has gone on. But within that, it’s kind of opening up the space for going like, well, this also suggests maybe you’ve done some stuff. And it also suggests that you haven’t gotten all the way there. This is very normal. This means
Justin Stockton (24:29)
Yep. Yep.
Mark Miller (24:31)
you care. This means that you’re starting to move the needle. It also means that you’re
A human being trying to code something and it’s not going to be perfect. Um, but you’re thinking about it early on, you’re communicating to other people where it is, so that if somebody grabs it, if somebody f you know forks it and wants to um build on top of it, they know where the accessibility piece stands when they do that. I think it’s fantastic. And I think you you
Justin Stockton (24:58)
Yeah, no, it’s awesome.
Mark Miller (25:00)
look at YouTube and you look at GitHub, and these are just two great examples of
large things that we use all day going like, Yeah, hey, no, we’re gonna throw this out there. And we’re gonna lead, lead by example.
Justin Stockton (25:15)
Yeah, no, it’s awesome. I mean, that it’s just another way for, because I very much believe in open source and a lot of the stuff that GitHub promotes through that. ah
Mark Miller (25:31)
Mm-hmm.
Justin Stockton (25:32)
But just the idea that now accessibility is out there, they’re promoting it, they’re trying to get people to think about it, and that it’s as important coming up.
Having your project have an accessibility statement is as important as defining the license that your code is gonna be sourced under.
Mark Miller (25:53)
Exactly.
Justin Stockton (25:55)
Of how do you want others to contribute to your project? Like it sits on that same footing now.
Mark Miller (26:01)
Mm and I think the other thing is is this is really accessibility, right? This is this is real and this is admitting the reality behind accessibility. So they’re not coming in and saying like we’ve built a scanner or or here’s a tool to go make your stuff better. They’re going What’s important here is that you communicate and that you communicate um what you’ve
i in that in i in communicating there’s an assumption that you’ve done something. There’s another major accessibility company that I just read uh today has come out with an AI tool and it’s it’s it’s interesting because it’s a shift left tool, so that’s kinda interesting. But it claim it’s claiming, and I’m saying claiming because I haven’t validated it, that it’s it’s able to catch more than traditional scanning
Tools can, and everybody wants the button, right? Every time somebody thinks about accessibility, they’re looking for that big red button that uh staples, was it staples that had the big red button and
Justin Stockton (27:13)
I’m hearing? Yeah. The easy button.
Mark Miller (27:16)
the easy button? They’re looking for the big red easy button to smack for accessibility, and everybody’s building something that’s
Feels a little closer to that easy button, but it’s not. It’s not there. Because if it catches 40 or 50 percent of the issues, who cares? You still need this kind of communication. You still need to consider doing manual reviews, right? And that that’s what I love about both of these things is that communicative nature. Accessibility is not per perfect. That button does not exist. So let’s communicate.
and incrementally improve. And by communicating, we allow people to understand and incrementally improve. Improve. Does that
Justin Stockton (28:06)
Yep.
Mark Miller (28:06)
make sense?
Justin Stockton (28:07)
Yeah. I agree, we agree.
Mark Miller (28:09)
And I just love that
signaling in the midst of this AI world where people are like, we can catch more issues now. I don’t care. Doesn’t matter to me. 30, 40, 50%. Who cares? It doesn’t turn off the need for a manual audit, so it doesn’t take that effort away. And you still need to communicate. It doesn’t take the need away from the communicator. It almost reduces the effort by nothing. Right. In a shift left, I sort of agree with it because um you’re catching more issues before they reach production. You know, you’re you’re th this
So I don’t mean to be that that negative on it.
Justin Stockton (28:40)
I
like to phrase it that it’s all about making sure that you’ve addressed the accessibility issues so that when you sit down for that audit or for accessibility testing with an actual person, you’re not embarrassed. How can we keep pushing to find more things through systematic, programmatic reviews of the code that
Mark Miller (29:08)
Mm-hmm.
Justin Stockton (29:09)
allows us to address those things so that we find less things in audit, that, or so
Mark Miller (29:14)
Yes.
Justin Stockton (29:14)
that when we do user testing that we’re not embarrassed by like having someone come down, sit in a room, bring their laptop and everything in to fire up a thing and then get stuck on a modal dialogue that’s not accessible. Like you don’t want to, you don’t want that scenario to occur. That’s why we test.
Mark Miller (29:32)
Well, I think the real argument for those things too is is more of an ROI argument, right? Like if you catch stuff in that testing process, whether your automated tool is catching more of it, whether you’ve got a uh robust manual aspects of your testing, they’re catching more of it. Like any anything you can layer on that’s gonna catch more stuff, like pe y organizations look at accessibility audits and they go, you know, we don’t have the budget.
And they look at that as the expensive thing. It’s not the expensive thing. The expensive thing is a ton of issues found in an accessibility audit. Why? Because the most expensive issues are the ones found in production. So anything that you can do, any any time, money process that you can put in place to reduce the number of issues before they reach production is, and that’s where these tools and and if and if I were the ones writing the marketing around it, that’s where I would focus is save your.
Company money by finding these things where they’re inexpensive to address and don’t let them find their way to production. You want to, in air quotes, waste your money on an audit because you want to do an audit and have it come through and say, Yeah, we found two things. And you know, really? You know, that much money to find two things? Yes, that’s good. Because the
Justin Stockton (30:45)
you
Mark Miller (30:46)
amount of money it costs you to audit is the least of your financial problems. And the more things sit,
and build and are not caught in production or or post you know pre production.
the more that debt builds up. And that’s what people don’t realize is that you don’t want to you don’t want
To not ignore, not communicate. We’re talking about communicating, right? Through the accessibility tags, through the accessibility markdown statements, um, or the accessibility statements and markdown on on GitHub. You gotta communicate these things and you’ve got to you’ve got to address these things and anything that you do address is better than anything that you don’t address. Like that’s the that’s kind of the full stop of it.
Justin Stockton (31:33)
Well, there’s also a cost afterwards of adopting the changes. Like I’m working on a project right now where they built something in a component library. Component library is great, but it’s got some accessibility issues in it. And
Mark Miller (31:46)
Mm-hmm.
Justin Stockton (31:47)
as we’re going through and fixing things for it, uh we’re defining like, you probably should not have named these things the way that you did because it has some unattended consequences for screen readers, for the browsers, et
Mark Miller (32:00)
Mm-hmm.
Justin Stockton (32:00)
cetera.
And so we need to change that. when we, when we, that’s now a breaking change in the component library. And so everyone that uses their component library is going to have, is going to have to go into their code and update their code to now call the correct properties and attributes and things. So.
Mark Miller (32:21)
And that, my friend, is a great example of accessibility debt. Right.
Justin Stockton (32:24)
Mm-hmm. Yeah.
Mark Miller (32:26)
What if that component library was audited? What if you found the budget and you had a third party expert come
Justin Stockton (32:34)
Mm-hmm.
Mark Miller (32:35)
in and look through that component library and catch that on the front end?
Or or in the beginning, you know?
Justin Stockton (32:39)
Yep. Yeah.
Mark Miller (32:41)
Yep. And that’s just one example. You
Justin Stockton (32:44)
That’s one example.
Mark Miller (32:45)
said something I’m working on now. There’s an example of something you’re doing right now. Never
Justin Stockton (32:49)
right now.
Mark Miller (32:50)
mind something you did before, never mind something you’re gonna do in the future. Those will be Okay, this that it’s that now. Yeah. I love how
Justin Stockton (32:52)
We will hang up and I will go back to continuing to do it. It is that. When now? Now. Soon.
Mark Miller (33:04)
accessibility statements on GitHub and and YouTube playable.
you know, accessible tags and the lawsuits got us talking about accessibility debt. Who knew we’d end up there? But all of it’s related. All of it’s related. So all right.
Justin Stockton (33:15)
Yeah, that’s where the conversation goes. Yeah. Oh, when
was GitHub? When it was launched?
Mark Miller (33:23)
Two two
thousand eight.
Justin Stockton (33:25)
So my account was created November 20th, 2010.
Mark Miller (33:31)
So it was around for two years before you caught on? That sounds about right though. Isn’t it usually
Justin Stockton (33:34)
But it’s been almost.
Mark Miller (33:37)
take t about two years for something to kinda catch on?
Justin Stockton (33:40)
I’m coming up on my 16th GitHub birthday. My GitHub account will be able to drive soon.
Mark Miller (33:47)
Oh.
What
Justin Stockton (33:49)
with AI.
Mark Miller (33:50)
Wait
to wait to wait till uh wait till like you know a few more years when it can drink. That’s when you’re that’s when you’re in trouble.
Justin Stockton (33:55)
It’s That’s right.
Mark Miller (33:59)
That’s you don’t want to get into that birthday. Oh, I just pulled my headphones out. Well, what do you think? Did we do it?
Justin Stockton (34:08)
I think we did it.
Mark Miller (34:09)
Yeah.
Justin Stockton (34:09)
Think we’re good?
Mark Miller (34:10)
All right. Well, thank you, Justin. Another great episode. And now that we have broken down accessibility for you, we hope you go forth and keep it accessible.
About the authors
Mark Miller
Founder & CEO at Inclusion Impact Accessibility
Mark SMiller is a digital accessibility consultant who helps organizations build accessible, inclusive digital experiences. He speaks regularly at industry conferences,, CSUN, CVENt and apperes on many webinars and podace. , He trains teams on practical, sustainable accessibility workflows.
Justin Stockton
Principal Accessibility Architect at Inclusion Impact Accessibility
Justin has 25+ years of accessibility experience spanning software development and product management. His career began working on federal accessibility initiatives, including Disability.gov and the U.S. Access Board. He has led accessibility audits for global enterprises, architected innovative audit tools, and managed enterprise accessibility platforms serving 1000s of users.


Comments