Recherche avancée

Sur d’autres sites (4451)

• How (and Why) to Run a Web Accessibility Audit in 2024

  7 mai 2024, par Erin

  When most businesses design their websites, they primarily think about aesthetics, not accessibility. However, not everyone who visits your website has the same abilities or access needs. Eight percent of the US population has visual impairments.

  The last thing you want is to alienate website visitors with a bad experience because your site isn’t up to accessibility standards. (And with growing international regulation, risk fines or lawsuits as a result.)

  A web accessibility audit can help you identify and fix any issues for users with impaired vision, hearing or other physical disabilities. In this article, we’ll cover how to conduct such an audit efficiently for your website in 2024.

  What is a web accessibility audit ?

  A web accessibility audit is a way to evaluate the usability of your website for users with visual, auditory or physical impairments, as well as cognitive disabilities or neurological issues. The goal is to figure out how accessible your website is to each of these affected groups and solve any issues that come up.

  To complete an audit, you use digital tools and various manual accessibility testing processes to ensure your site meets modern web accessibility standards.

  Why is a web accessibility audit a must in 2024 ?

  For far too long, many businesses have not considered the experiences of those with disabilities. The growing frustrations of affected internet users have led to a new focus on web accessibility laws and enforcement.

  Lawsuits related to the ADA (Americans with Disabilities Act) reached all-time highs in 2023 — over 4,500 digital-related lawsuits were filed. The EU has also drawn up the European Accessibility Act (EAC), which goes into effect in June 2025.

  But at the end of the day, it’s not about accessibility legislation. It’s about doing right by people.

  

  This video by voice actor, YouTuber, and surfer Pete Gustin demonstrates why accessibility measures are so important. If buttons, navigation and content sections aren’t properly labelled, sight-impaired people who rely on speech-to-text to browse the web can’t comfortably interact with your site.

  And you’re worse off for it. You can lose some of your best customers and advocates this way. 

  With stronger enforcement of accessibility regulations in the US and new regulations coming into effect in the EU in 2025, the time to act is now. It’s not enough to “keep accessibility in mind” — you must take concrete steps to improve it.

  Who should lead a web accessibility audit ?

  Ideally, you want to hire a third-party web accessibility expert to lead the audit. They can guide you through multiple stages of manual accessibility testing to ensure your site meets regulations and user needs. 

  Experienced accessibility auditors are familiar with common pitfalls and can help you avoid them. They ensure you meet the legal requirements with proper solutions, not quick fixes.

  If this isn’t an option, find someone with relevant experience within your company. And involve someone with “skin in the game” in the process. Hire someone with visual impairments to usability test your site. Don’t just do automated tests or “put yourself in their shoes.” Make sure the affected users can use your site without issues.

  Automated vs. manual audits and the danger of shortcuts

  While there are automated audits, they only check for the bare minimum :

  • Do your images have alt tags ? (They don’t check if the alt tag is descriptive or just SEO junk text.)
  • Are clickable buttons identified with text for visually impaired users ?
  • Is your text size adjustable ?
  • Are your background and foreground colours accessible for colour-blind users ? Is there a sufficient contrast ratio ?

  

  They don’t dive into the user journey (and typically can’t access login-locked parts of your site). They can be a good starting point, but it’s a bad idea to rely completely on automated audits.

  They’ll miss more complex issues like :

  • Dynamic content and animated elements or videos that could put people with epilepsy at risk of seizures
  • A navigational flow that is unnecessarily challenging for users with impairments
  • Video elements without proper captions

  So, don’t rely too much on automated tests and audits. Many lawsuits for ADA infractions are against companies that think they’ve already solved the problem. For example, 30% of 2023 lawsuits were against sites that used accessibility overlays.

  Key elements of the Web Content Accessibility Guidelines (WCAG)

  The international standard for web accessibility is the Web Content Accessibility Guidelines (WCAG). In the most recent version, WCAG 2.2, there are new requirements for visual elements and focus and other updates.

  Here’s a quick overview of the key priorities of WCAG :

  

  Perceivable : Any user can read or listen to your site’s content

  The first priority is for any user to be able to perceive the actual content on your site. To be compliant, you need to make these adjustments and more :

  • Use text that scales with browser settings.
  • Avoid relying on colour contrasts to communicate something.
  • Ensure visual elements are explained in text.
  • Offer audio alternatives for things like CAPTCHA.
  • Form fields and interactive elements are properly named.

  Operable : Any user can navigate the site and complete tasks without issue

  The second priority is for users to navigate your website and complete tasks. Here are some of the main considerations for this section :

  • Navigation is possible through keyboard and text-to-speech interfaces.
  • You offer navigation tools to bypass repeated blocks of content.
  • Buttons are properly titled and named.
  • You give impaired users enough time to finish processes without timing out.
  • You allow users to turn off unnecessary animations (and ensure none include three flashes or more within one second).
  • Links have a clear purpose from their alt text (and context).

  Understandable : Any user can read and understand the content

  The third priority is making the content understandable. You need to communicate as simply and as clearly as possible. Here are a few key points :

  • Software can determine the default language of each page.
  • You use a consistent method to explain jargon or difficult terms.
  • You introduce the meaning of unfamiliar abbreviations and acronyms.
  • You offer tools to help users double-check and correct input.
  • The reading grade is not higher than grade 9. If it is, you must offer an alternative text with a lower grade.
  • Use consistent and predictable formatting and navigation.

  This intro to accessibility guidelines should help you see the wide range of potential accessibility issues. Accessibility is not just about screen readers — it’s about ensuring a good user experience for users with a wide range of disabilities.

  Note : If you’re not hiring a third-party expert for the manual accessibility audit, this introduction isn’t enough. You need to familiarise yourself with all 50 success criteria in WCAG 2.2.

  How to do your first web accessibility audit

  Ready to find and fix the accessibility issues across your website ? Follow the steps outlined below to do a successful accessibility audit.

  Start with an automated accessibility test

  To point you in the right direction, start with a digital accessibility checker. There are many free alternatives, including :

  • Accessibility Checker
  • Silktide accessibility checker
  • AAArdvark

  When choosing a tool, check it’s up-to-date with the newest accessibility guidelines. Many accessibility evaluation tools are still based on the WCAG 2.1 version rather than WCAG 2.2.

  The tool will give you a basic evaluation of the accessibility level of your site. A free report can quickly identify common issues with navigation, labelling, colour choices and more. 

  But this is only good as a starting point. Remember that even paid versions of these testing tools are limited and cannot replace a manual audit.

  Look for common issues

  The next step is to manually look for common issues that impact your site’s level of accessibility :

  • Undescriptive alt text
  • Colour combinations (and lack of ability to change background and foreground colours)
  • Unscalable text
  • Different site content sections that are not properly labelled

  The software you use to create your site can lead to many of these issues. Is your content management system (CMS) compliant with ADA or WCAG ? If not, you may want to move to a CMS before continuing the audit.

  Pinpoint customer journeys and test them for accessibility 

  After you’ve fixed common issues, it’s essential to put the actual customer journey to the test. Explore your most important journeys with behavioural analytics tools like session recordings and funnel analysis.

  Analysing funnel reports lets you quickly identify each page that usually contributes to a sale. You will also have an overview of the most popular funnels to evaluate for accessibility.

  If your current web analytics platform doesn’t offer behavioural reports like these, Matomo can help. Our privacy-friendly web analytics solution includes funnel reports, session recordings, A/B testing, form analytics, heatmaps and more.

  Try Matomo for Free

  Get the web insights you need, without compromising data accuracy.

  Start for free

  No credit card required

  If you don’t have the budget to test every page individually, this is the perfect place to start. You want to ensure that users with disabilities have no issues completing the main tasks on your site. 

  Don’t focus solely on your web pages 

  Accessibility barriers can also exist outside of your standard web pages. So ensure that other file formats like PDFs and videos are also accessible. 

  Remember that downloadable materials are also part of your digital experience. Always consider the needs of individuals with disabilities when accessing things like case studies or video tutorials. 

  Highlight high-priority issues in a detailed report

  To complete the audit, you need to summarise and highlight high-priority issues. In a larger company, this will be in the form of a report. W3’s Web Accessibility Initiative offers a free accessibility report template and an online tool to generate a report.

  For smaller teams, it may make sense to input issues directly into the product backlog or a task list. Then, you can tackle the issues, starting with high-priority pages identified earlier in this process.

  Avoid quick fixes and focus on sustainable improvement

  As mentioned, AI-powered overlay solutions aren’t compliant and put you at risk for lawsuits. It’s not enough to install a quick accessibility tool and pat yourself on the back.

  And it’s not just about accessibility compliance. These solutions provide a disjointed experience that alienates potential users. 

  The point of a digital accessibility audit is to identify issues and provide a better experience to all your users. So don’t try to cut corners. Do the work required to implement solutions that work seamlessly for everyone. Invest in a long-term accessibility remediation process.

  Deliver a frictionless experience while gaining insight into your users

  An accessibility audit is crucial to ensure an inclusive experience — that a wide variety of users can read and interact with your site.

  But what about the basic usability of your website ? Are you sure the experience is without friction ? Matomo’s behavioural analytics tools can show how users interact with your website.

  For example, heatmaps can show you where users are clicking — which can help you identify a pattern, like many users mistaking a visual element for a button.

  Plus, our privacy-friendly web analytics are compliant with GDPR, CCPA and other data privacy regulations. That helps protect you against privacy-related lawsuits, just as an accessibility audit protects you against ADA lawsuits.

  And it never hurts that your users know you respect their privacy. Try Matomo free for 21-days. No credit card required.

  Try Matomo for Free

  21 day free trial. No credit card required.

  
  

  Your email address
  

  Your website address
  

  Your Analytics subdomain will be .matomo.cloud (change)

  Choose your analytics subdomain
  

  .matomo.cloud

  I accept the terms and conditions and data processing agreement (DPA)

  
  Your information will be used to create an account on our cloud service. For more information please consult our privacy policy.
  
  
  

  Start improving your websites now

  

• RaspberryPi HLS streaming with nginx and ffmpeg ; v4l2 error : ioctl(VIDIOC_STREAMON) : Protocol error

  22 janvier 2021, par Mirco Weber

  I'm trying to realize a baby monitoring with a Raspberry Pi (Model 4B, 4GB RAM) and an ordinary Webcam (with integrated Mic).
I followed this Tutorial : https://github.com/DeTeam/webcam-stream/blob/master/Tutorial.md

  


  Shortly described :

  


  

  1. I installed and configured an nginx server with rtmp module enabled.

  


  2. I installed ffmpeg with this configuration —enable-gpl —enable-nonfree —enable-mmal —enable-omx-rpi

  


  3. I tried to stream ;)

  


  


  The configuration of nginx seems to be working (sometimes streaming works, the server starts without any complication and when the server is up and running, the webpage is displayed).
The configuration of ffmpeg seems to be fine as well, since streaming sometimes works...

  


  I was trying a couple of different ffmpeg-commands ; all of them are sometimes working and sometimes resulting in an error.
The command looks like following :

  


  ffmpeg -re
-f v4l2
-i /dev/video0
-f alsa
-ac 1
-thread_queue_size 4096
-i hw:CARD=Camera,DEV=0
-profile:v high
-level:v 4.1
-vcodec h264_omx
-r 10
-b:v 512k
-s 640x360
-acodec aac
-strict
-2
-ac 2
-ab 32k
-ar 44100
-f flv
rtmp://localhost/show/stream;


  


  Note : I rearranged the code to make it easier to read. In the terminal, it is all in one line.
Note : There is no difference when using -f video4linux2 instead of -f v4l2

  


  The camera is recognized by the system :

  


  pi@raspberrypi:~ $ v4l2-ctl --list-devices
bcm2835-codec-decode (platform:bcm2835-codec):
    /dev/video10
    /dev/video11
    /dev/video12

bcm2835-isp (platform:bcm2835-isp):
    /dev/video13
    /dev/video14
    /dev/video15
    /dev/video16

HD Web Camera: HD Web Camera (usb-0000:01:00.0-1.2):
    /dev/video0
    /dev/video1


  


  When only using -i /dev/video0, audio transmission never worked.
The output of arecord -L was :

  


  pi@raspberrypi:~ $ arecord -L
default
    Playback/recording through the PulseAudio sound server
null
    Discard all samples (playback) or generate zero samples (capture)
jack
    JACK Audio Connection Kit
pulse
    PulseAudio Sound Server
usbstream:CARD=Headphones
    bcm2835 Headphones
    USB Stream Output
sysdefault:CARD=Camera
    HD Web Camera, USB Audio
    Default Audio Device
front:CARD=Camera,DEV=0
    HD Web Camera, USB Audio
    Front speakers
surround21:CARD=Camera,DEV=0
    HD Web Camera, USB Audio
    2.1 Surround output to Front and Subwoofer speakers
surround40:CARD=Camera,DEV=0
    HD Web Camera, USB Audio
    4.0 Surround output to Front and Rear speakers
surround41:CARD=Camera,DEV=0
    HD Web Camera, USB Audio
    4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=Camera,DEV=0
    HD Web Camera, USB Audio
    5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=Camera,DEV=0
    HD Web Camera, USB Audio
    5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=Camera,DEV=0
    HD Web Camera, USB Audio
    7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
iec958:CARD=Camera,DEV=0
    HD Web Camera, USB Audio
    IEC958 (S/PDIF) Digital Audio Output
dmix:CARD=Camera,DEV=0
    HD Web Camera, USB Audio
    Direct sample mixing device
dsnoop:CARD=Camera,DEV=0
    HD Web Camera, USB Audio
    Direct sample snooping device
hw:CARD=Camera,DEV=0
    HD Web Camera, USB Audio
    Direct hardware device without any conversions
plughw:CARD=Camera,DEV=0
    HD Web Camera, USB Audio
    Hardware device with all software conversions
usbstream:CARD=Camera
    HD Web Camera
    USB Stream Output


  


  that's why i added -i hw:CARD=Camera,DEV=0.

  


  As mentioned above, it worked very well a couple of times with this configuration and commands.
But very often, i get the following error message when starting to stream :

  


  pi@raspberrypi:~ $ ffmpeg -re -f video4linux2 -i /dev/video0 -f alsa -ac 1 -thread_queue_size 4096 -i hw:CARD=Camera,DEV=0 -profile:v high -level:v 4.1 -vcodec h264_omx -r 10 -b:v 512k -s 640x360 -acodec aac -strict -2 -ac 2 -ab 32k -ar 44100 -f flv rtmp://localhost/show/stream
ffmpeg version N-100673-g553eb07737 Copyright (c) 2000-2021 the FFmpeg developers
  built with gcc 8 (Raspbian 8.3.0-6+rpi1)
  configuration: --enable-gpl --enable-nonfree --enable-mmal --enable-omx-rpi --extra-ldflags=-latomic
  libavutil      56. 63.101 / 56. 63.101
  libavcodec     58.117.101 / 58.117.101
  libavformat    58. 65.101 / 58. 65.101
  libavdevice    58. 11.103 / 58. 11.103
  libavfilter     7. 96.100 /  7. 96.100
  libswscale      5.  8.100 /  5.  8.100
  libswresample   3.  8.100 /  3.  8.100
  libpostproc    55.  8.100 / 55.  8.100
[video4linux2,v4l2 @ 0x2ea4600] ioctl(VIDIOC_STREAMON): Protocol error
/dev/video0: Protocol error


  


  And when I'm swithing to /dev/video1 (since this was also an output for v4l2-ctl --list-devices), I get the following error message :

  


  pi@raspberrypi:~ $ ffmpeg -re -f v4l2 -i /dev/video1 -f alsa -ac 1 -thread_queue_size 4096 -i hw:CARD=Camera,DEV=0 -profile:v high -level:v 4.1 -vcodec h264_omx -r 10 -b:v 512k -s 640x360 -acodec aac -strict -2 -ac 2 -ab 32k -ar 44100 -f flv rtmp://localhost/show/stream
ffmpeg version N-100673-g553eb07737 Copyright (c) 2000-2021 the FFmpeg developers
  built with gcc 8 (Raspbian 8.3.0-6+rpi1)
  configuration: --enable-gpl --enable-nonfree --enable-mmal --enable-omx-rpi --extra-ldflags=-latomic
  libavutil      56. 63.101 / 56. 63.101
  libavcodec     58.117.101 / 58.117.101
  libavformat    58. 65.101 / 58. 65.101
  libavdevice    58. 11.103 / 58. 11.103
  libavfilter     7. 96.100 /  7. 96.100
  libswscale      5.  8.100 /  5.  8.100
  libswresample   3.  8.100 /  3.  8.100
  libpostproc    55.  8.100 / 55.  8.100
[video4linux2,v4l2 @ 0x1aa4610] ioctl(VIDIOC_G_INPUT): Inappropriate ioctl for device
/dev/video1: Inappropriate ioctl for device


  


  When using the video0 input, the webcam's LED that recognizes an access is constantly on. When using video1not.

  


  After hours and days of googling and tears and whiskey, for the sake of my liver, my marriage and my physical and mental health, I'm very sincerly asking for your help...
What the f**k is happening and what can I do to make it work ???

  


  Thanks everybody :)

  


  UPDATE 1 :

  


  

  1. using the full path to ffmpeg does not change anything...

  


  2. /dev/video0 and /dev/video1 have access rights for everybody

  


  3. sudo ffmpeg ... does not change anything as well

  


  4. the problem seems to be at an "early stage". Stripping the command down to ffmpeg -i /dev/video0 results in the same problem

  


  


  UPDATE 2 :
  
It seems that everything is working when I first start another Application that needs access to the webcam and then ffmpeg...
Might be some driver issue, but when I'm looking for loaded modules with lsmod, there is absolutely no change before and after I started the application...
Any help still appreciated...

  


  UPDATE 3 :
  
I was checking the output of dmesg.
  
When I started the first application I received this message :
  
uvcvideo: Failed to query (GET_DEF) UVC control 12 on unit 2: -32 (exp. 4).

  And when I started ffmpeg, nothing happend but everything worked...

  


• Join us at MatomoCamp 2024 world tour edition

  13 novembre 2024, par Daniel Crough — Uncategorized

  Join us at MatomoCamp 2024 world tour edition, our online conference dedicated to Matomo Analytics—the leading open-source web analytics platform that prioritises data privacy.

  • 🗓️ Date : 14 November 2024
  • 🌐 Format : 24-hour virtual conference accessible worldwide
  • 💰 Cost : Free and no need to register

  Event highlights

  Opening ceremony

  Begin the day with a welcome from Ronan Chardonneau, co-organiser of MatomoCamp and customer success manager at Matomo.

  View session | iCal link

  Keynote : “Matomo by its creator”

  Attend a special session with Matthieu Aubry, the founder of Matomo Analytics. Learn about the platform’s evolution and future developments.

  View session | iCal link

  Explore MatomoCamp 2024’s diverse tracks and topics

  MatomoCamp 2024 offers a wide range of topics across several tracks, including using Matomo, integration, digital analytics, privacy, plugin development, system administration, business, other free analytics, use cases, and workshops and panel talks.

  Featured sessions

  1. Using AI to fetch raw data with Python

  Speaker : Ralph Conti
  Time : 14 November, 12:00 PM UTC

  Discover how to combine AI and Matomo’s API to create unique reporting solutions. Leverage Python for advanced data analysis and unlock new possibilities in your analytics workflow.

  View session | iCal link

  2. Supercharge Matomo event tracking with custom reports

  Speaker : Thomas Steur
  Time : 14 November, 2:00 PM UTC

  Learn how to enhance event tracking and simplify data analysis using Matomo’s custom reports feature. This session will help you unlock the full potential of your event data.

  View session | iCal link

  3. GDPR with AI and AI Act

  Speaker : Stefanie Bauer
  Time : 14 November, 4:00 PM UTC

  Navigate the complexities of data protection requirements for AI systems under GDPR. Explore the implications of the new AI Act and receive practical tips for compliance.

  View session | iCal link

  4. A new data mesh era !

  Speaker : Jorge Powers
  Time : 14 November, 4:00 PM UTC

  Explore how Matomo supports the data mesh approach, enabling decentralised data ownership and privacy-focused analytics. Learn how to empower teams to manage and analyse data without third-party reliance.

  View session | iCal link

  5. Why Matomo has to create a MTM server side : The future of data privacy and user tracking

  Panel discussion
  Time : 14 November, 6:00 PM UTC

  Join experts in a discussion on the necessity of server-side tag management for enhanced privacy and compliance. Delve into the future of data privacy and user tracking.

  View session | iCal link

  6. Visualisation of Matomo data using external tools

  Speaker : Leticia Rodríguez Morado
  Time : 14 November, 8:00 PM UTC

  Learn how to create compelling dashboards using Grafana and Matomo data. Enhance your data visualisation skills and gain better insights.

  View session | iCal link

  7. Keep it simple : Tracking what matters with Matomo

  Speaker : Scott Fillman
  Time : 14 November, 9:00 PM UTC

  Discover how to focus on essential metrics and simplify your analytics setup for more effective insights. Learn tactics for a powerful, streamlined Matomo configuration.

  View session | iCal link

  Stay connected

  Stay updated with the latest news and announcements :

  • Twitter : @MatomoCamp
  • YouTube : @MatomoCamp
  • Official website : matomocamp.org

  Don’t miss out

  MatomoCamp 2024 world tour edition is more than a conference ; it’s a global gathering shaping the future of ethical analytics. Whether you aim to enhance your skills, stay informed about industry trends, or network with professionals worldwide, this event offers valuable opportunities.