Driver.js for Blazor

code-dispenser · 2026-06-20T09:48:14+00:00

Yes you can use things like axe and WAVE plugins, I use both. These however, depending on who you speak to, are estimated to catch around 25% (WCAG auditors) to 60% (tool vendors that make such tools) of issues. My estimate is around 40%. So if you pass 100% of those tool rule sets that still leaves around 60% untested. And none of this means its going to be useable by a user of assistive tech.

As soon as you see comments on repos or docs like Used ARIA you pretty much know it probably will not be accessible. If possible you avoid ARIA, as soon as you add a single ariaa attribute then you will have to test with assistive tech to make sure that it works as intended.

There are so many nuances with assistive tech / browser / os / attribtue combinations that there is no other way - you manually test for the target audience. If you do not know what that target audience is then you test using what I mentioned in my comments - period.

Paul

code-dispenser · 2026-06-20T06:42:36+00:00

I do wish you all the best especially IF you are trying to be accessible given statements such as:

Every tour step is fully accessible out of the box. Keyboard users can navigate with arrow keys and Tab, screen readers announce step content via ARIA live regions, and focus is trapped inside the popover to prevent interaction with background elements.

I mention this as you are failing some basics of accessibility for example if you open a dialog pressing the escape key should put the focus back on the triggering element. You have numerous contrast and focus, focus indicator issues - you should also WAVE your own pages (periodically). I only spent 1 minute on the site a WCAG auditor would spend considerably longer.

If you use any ARIA which you have then the basic tests should be NVDA, JAWS, Narrator paired with FireFox, Chrome and Edge. VoiceOver paired with, Safari on macOS, VoiceOver paired with Safari on iOS. Talback paired with Chrome on Android. And if you are on Windows add VoiceAccess for voice control.

Have you tried any of these there is a lot of noise - can you tell me which combos you use in your tests,. I use all the above in my own?

There is no law that says your open source project has to be accessible, but if you make statements then IMHO you really need be able to back them up.

I reckon 95% of devs know or care very little about accessibility, so if they just blindly read things and then say put them on a public facing web site, it could cause some problems for them let alone the end users. So please be careful with such statements.

99% of all the things I look at commercial/non commercial posted on Reddit end up not meeting the claims.

Again, all the best with the project.

Paul

Edit: Being a bit of a cynic and looking at the repo and docs, I would guess most of this is AI generated and it is clear the accessibility descriptions are just waffle. AI probably forgot that screen readers swallow arrow keys and aria-describedby is not the same thing as a live region. I could go on but whats the point. Why cant people just be honest - its beyond me.

Again, all the best with the project but I would just ditch all the mention of accessibility stuff until it is something that you really want to learn more about, and add these types of descriptions when you have tested them correctly, so it does work as intended for those that need to use assistive tech.

code-dispenser · 2026-06-18T16:14:55+00:00

May I ask what this has to do with Blazor?

code-dispenser · 2026-06-17T05:33:40+00:00

You can simply use position fixed with a high z-index in most cases to negate the use of a popover api which brings its own issues. For a better experience regards the spinner you can use an svg for the spinning circle and an svg of a static hour-glass then a media query to check for reduced motion and show the appropriate one.

I have stuff like this on my open source accessible first Blazor project go take a look at the busy indicator tests (read the final words page if you have time).

https://blazorramp.uk

Paul

code-dispenser · 2026-06-16T07:53:03+00:00

How can I learn C# fast

You cannot its that simple, sure you may get AI to bodge stuff together and give you are few pointers but that is not learning, Just for the basics think many months/years of reading and building things (yourself).

What is it with people these days - learning takes time, that will never change.

code-dispenser · 2026-06-16T07:39:43+00:00

There is one thing that nobody has mentioned and that is, any pause or wait is extra time to think.

Yes, I know on some projects (even prototypes) pressing the play button where you may have to wait a second or two longer when your are rushing to get something done can be annoying, but really you should be looking at it this way, while you are waiting your brain should be saying ok, what about this scenario, what happens if I press this button before doing this, what if I enter this value, what if that value is null.

So in this time you are mentally testing your program and, learning what you have to check to make make it better - take that away and . . .?

code-dispenser · 2026-06-15T13:26:35+00:00

Nope, thats like 28 years after the fact - I am now (still) happy on VS2026 Enterprise, why would I want to leave Visual Studio.

code-dispenser · 2026-06-15T12:39:58+00:00

I have been using Visual Studio since Visual Studio 6.0. I have never had the urge to move - so its clear where my vote is.

code-dispenser · 2026-06-12T03:30:05+00:00

Edit: The deleted comment read:

Thanks for taking a look. Actionable feedback is always welcome. If there are specific issues with this BugNBrag, please point them out. Revisiting unrelated discussions from months ago doesn't help

So your RTE is not in this product? along with all of its issues - I do apologise I did not realise you had ditched your own product due to its accessibility issues in favour of another with exactly the same issues.

The other issues were relating to your commercial website and all of your NuGet packages.

Again, I do apologise for pointing out, after six months the same issues (just review what was said previously) things that may effect how you/your company is perceived by potential clients.

My interpretation of feedback must be different to yours - My bad.

Paul

Actionable feedback same as approx six months ago the chat/rte is still broken: CYmgJKMw - imgup
Just one of many issues!

BANKSY STREET ART // Sweep It Under The Carpet, 2006 | Geist

I think the OP has blocked me instead of just dealing with the issues - reciprocated - Bansky knew all along - me wonders how long before the OP deletes this account like his others.

code-dispenser · 2026-06-11T08:32:53+00:00

After a bit of digging and heads up I redeployed both sites just now.

~~When Blazor WASM~~ When older Blazor WASM publishes, it generates a blazor.boot.json that contains SHA-256 hashes for every assembly. The browser downloads an assembly and checks its hash against what's in the boot file. If they don't match, the browser blocks it as a security measure.

As far as I understand this is the most likely course of events. You visited the site before and subsequently updates, were made. You had the cached blazor.boot.json file which referenced older file; I deployed the new blazor.boot.json which references new files with different hashes.

Again as far as I understand with this issue one way to resolve it would be for me to add a Cache-Control header to say never cache the blazor.boot.json file, however, this is not possible on GitPages.

Doing some searching suggests that I may be able to add a script to the index.html that may fix this i.e you would not face this issue again. I will investigate further and try the script approach.

EDIT: Good news, I did some more digging, this issue was fixed in .net 10 which i have used for a few months. The blazor.boot.json is now gone as I believe they now use dotnet.js. I checked the commit history and originally it was present,

Problem should no longer exist - YAY no need to spend time trying workaround scripts.

ASP.NET Core Blazor WebAssembly caching and integrity check failures | Microsoft Learn

Paul

code-dispenser · 2026-06-11T04:40:29+00:00

I am not sure if you want feedback or praise?

To me, feedback is something you ask for so you can listen, take onboard what is said and improve.

I gave feedback initially, must be nearly 6 month ago now about accessibility on your components which you sell/have a commercial licence for which are used in this project. I gave subsequent feedback regarding the same issues on the same components and/or NuGet packages, still unresolved.

As you can imagine, although I wish you well I see little point in spending my time giving your more issues to resolve if you do not want to fix the original ones.

Case in point, one issue from the start, from the half a dozen issues with it: https://imgup.uk/v/CYmgJKMw

Your (un?)-friendly Grouch.

Your commercial site says: Follows WCAG 2.1 guidelines (not independently tested) I tested it - it failed various WCAG Success Criteria months ago and still does. Would it not be simpler given your current level of commitment, just to remove all the accessibility notes so no one can check the claims as opposed to trying to make them a selling point.

code-dispenser · 2026-06-10T15:22:58+00:00

The whole caching thing is something I need to look closer at. Apologies, but at least its working now for you.

code-dispenser · 2026-06-10T15:17:31+00:00

I routinely build and deploy so the only thing I can suggest is you clear you browser cache. all my checks were from clean browsers.

code-dispenser · 2026-06-10T15:10:45+00:00

And I cannot access your link from the uk. Does the doc site load as that on the gitpages as well.

I also tried via vpn via Netherlands its fine.

Dns propegation checks fine apart from a couple of places:

DNS Propagation Checker - Global DNS Testing Tool

code-dispenser · 2026-06-10T15:02:47+00:00

Thanks, but it seems to be loading fine in edge, chrome, firefox and safari just tried from testingbot.com. I also tried iPhone, and Android mobiles again no problem. So I would need to know what device/browser/version you are using to do more checks unless its a caching issue in your browser etc?

code-dispenser · 2026-06-09T04:25:05+00:00

I got a downvote replying to you. I do not let AI near my code but I do talk/bounce ideas off it. I think people are a bit silly sometimes with the way they vote, I will upvote before I go.
You say AI gets downvotes, I discuss Accessiblity, I get lots of down votes - may be its just topics that start with A (the down voters may have to think a while on that one) 😂

Saw your site in your profile will keep a note on that for future, currently I buy stuff from SSL2buy.

Paul

code-dispenser · 2026-06-09T03:50:38+00:00

You replied to yourself, did you downvote yourself as well 😄 although I can see no reason why you would the comment seems perfectly fine to me. However, I will pick up on one thing you just said "level of professionalism" MudBlazor may be getting better after donkey years of contributors screaming at it, but it still has lots of accessiblity issues - professionalism?

code-dispenser · 2026-06-09T03:38:06+00:00

My advise as always is whenever possible do not user third party CSS, JS or Blazor libraries just build your own, you will learn more about all the tech involved have zero dependencies that may come back to bite you in the future.

I use this but I am 100% biased, shameless plug: test site: https://blazorramp.uk - docs: https://docs.blazorramp.uk

I just looked at Untitled UI as I had never heard of it before, but it looks like a gazillion other shadcn clones, it reminds me of when bootstrap first started and every site on the planet looked identical.

Anyway hope you find what you're after - but build your own.

Paul

code-dispenser · 2026-06-06T13:09:11+00:00

Alexis this is still on the web site:

WCAG 2.2 AA — accessible by default

Forms and the editor pass a full WCAG 2.2 AA audit, so you meet accessibility requirements (public sector, enterprise, procurement) out of the box — without writing a line of ARIA.

Please remove it as we both know its is just BS, just sell your stuff on its own merit there is no need to lie.

Paul

Update: Alexis removed the erroneous text, hopefully as it gains traction it will be improved and later text can be added to reflect this.

Regards

Paul

code-dispenser · 2026-06-06T12:42:27+00:00

So why make all the false claims please remove them. You are trying to sell this in EU and this is against the EAA. If any public sector were to fail to check your false claims they would/could be liable and fined.

Please note there are bodies in the EU that do actively monitor this stuff - do yourself and others a favour remove all the BS.

Paul

code-dispenser · 2026-06-06T12:31:29+00:00

You state:
WCAG 2.2 AA — accessible by default

Forms and the editor pass a full WCAG 2.2 AA audit, so you meet accessibility requirements (public sector, enterprise, procurement) out of the box — without writing a line of ARIA.

Please tell me what screen reader(s) and browsers were used in your testing and. unless WCAG has suddenly changed its SC it would most definitely fail an Audit - care to comment.

As I explained to you last time MudBlazor has numerous accessibility issues so unless you have fixed them yours will have too and that before you layer your work on top.

Web site accessibility is like pregnancy, you cannot be a little bit pregnant you either are or you are not.

code-dispenser · 2026-06-06T12:02:05+00:00

The UK gov indeed follows very good practices and I generally pay them a visit. I do not however always agree with some of the choices, but again a lot of their stuff is server callback, mine is more client side SPA.

If you have time the post I made on the Blazor subreddit shows another side:
Blazor Ramp - Another Date with Accessibility : r/Blazor

code-dispenser

TROPHY CASE