I continued working on aXeSiA in my spare time and improved it by adding new features like page complexity score and summary of summaries that takes this complexity into account.
At the same time I’ve also got the recordings from my presentation of aXeSiA on axe-hackathon 2021 (opens in new window) and from my answers to the questions that I got after the presentation of aXeSiA.
I noticed that captions for my answers were not so good and wanted to transcribe them here.
Questions about aXeSiA after presentation
- Question from the chat: Have you used aXeSiA on any project yet? If so, what has the experience been? Answer by me: This is totally new project, I’ve just tested it because I made it in a couple of weekend nights. Now, I am planning to use it on my audits, because I will do some auditing and it’s always a good start to start with automatic auditing and that’s why I wanted to have like multiple tools, so that I can also have some statistics and follow-up on evolution of fixes, accessibility fixes, and also to follow up on the search engine optimization (SEO) and other key point indicators (KPI).
- Question from the chat: How does it compare to Pally (Pa11y)? Is this to get access to multiple engines? Are there other benefits? Answer by me: Yes, that was the idea – to use multiple engines – like open source that allows pluggable modules and so you could also actually use it for end to end testing or maybe even unit testing. Not only accessibility, but my focus now was on accessibility. And I also see that it is very easy to implement third party API’s, like for example axe and also Tenon and others… So the idea is to have a lot of information and then some statistical, actually some statistical calculations that make you focus on the most problematic sites. I have also begun with some simple static analysis of code – to maybe push the most complex sites up front and to start looking at them for manual testing. The whole point here is actually to get most effective from our multiple automatic tests, to start and be more effective for manual testing. And maybe also integrate Google Analytics and take for example, top 100 pages and start with them. So yeah – I just like the idea of openness – to have open possibilities. And that Puppeteer and your brilliant axe and Siteimprove Alfa really enable us to do.
Feedback from the axe-con’s Deque axe-hackathon’s team
I’ve also got an email with the feedback from the axe-hackathon’s team and am publishing it here for reference;
Hi Bogdan,
Thank you for participating in this year’s axe-hackathon!
As you know, the projects we had this year were incredibly diverse and evaluating each one was no small feat. Especially aXeSiA, which layered several a11y technologies in a novel way.
What stood out to the jury about this project was the volume of useful data available to the user and the degree of overall automation. The feature showing pages with the greatest number of violations first in the reports was great as well. We’re looking forward to where aXeSia will go as development is continued!
Thank you so much for participating this year and for bringing such great energy. We hope that you continue to work on aXeSiA because it has a lot of potential to advance the mission of digital equality.
Hope to see you next year!
Sincerely,
The Deque axe-hackathon Team
It was nice to receive it and as mentioned – aXeSiA will not retire with axe-hackathon’s end and I will be using and improving it regularly.
