Project
Introduction
In the contemporary world, internet access has become a necessity for human beings. It is totally common for people to access news sites, social networks at any time of the day, whether to learn about the latest pronouncements of national or international politics, or to get in touch with that loved one who is far away. The fact is that the internet in addition to providing moments of fun and leisure, it is also a crucial tool for accessing information. Although it seems a trivial thing to do for people without disabilities, this simple act of seeking information can become a real complication if the person has a disability, whether physical or mental.
Thus, this project aims to assist in a minimal part of the development of software products, focusing on the web part that uses Hypertext Markup Language (HTML), so that it is possible to carry out tests, in a development environment to ensure that a minimum quantity accessibility is achieved by this product.
Objective
Create a tool capable of carrying out accessibility tests, simple, on pages with the HTML language, that is integrated into the DevOps pipeline.
Technology
The package was created using the python programming language on version 3 or higher
Dependencies
The package dependencies that will be installed automatically are:
- beautifulsoup4 ~= 4.9;
- py-w3c ~= 0.3
Installation
There are two ways to install and use the package, the first being installing directly from the pip repository using the command: pip install -i https://test.pypi.org/simple/ automated-accessibility-testing==1.0.0
The second form of installation would be from this repository needing to perform the clone and install locally from this command: git clone https://github.com/TCC2-Romeu/automated_accessibility_testing.git
Use
To use the package you can call the check_accessibility function and pass the html as a string, this way the package will perform all tests of the package in terms of accessibility in addition to a static validation of the html according to w3c, in case the user does not want to run some of the functions it can pass a list to the check_accessibility method where the listed functions will be ignored. At the end the user will receive a list of objects with the errors pointed out
License
The project license is: GPL3
Metadata
Release files for automated-accessibility-testing 1.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| automated_accessibility_testing-1.0.1.tar.gz | 4.0 kB | Without provenance | Details for automated_accessibility_testing-1.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| automated_accessibility_testing-1.0.1-py3-none-any.whl | Python 3 | none | any | Details for automated_accessibility_testing-1.0.1-py3-none-any.whl |
Total release size: 21.5 kB
Release files / automated_accessibility_testing-1.0.1.tar.gz
| Download URL | automated_accessibility_testing-1.0.1.tar.gz |
|---|---|
| Size | 4.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ca0055143301f31b621faf7166e7b27883694123e3ffe90568c0fd5b1bde5b3f
|
|
BLAKE2b-256 checksum How to use checksums |
3a0de810160ff900d1f6658cd31516eb85adacedaf79e0b234d498e8d6b9c57e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.25.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.54.1 CPython/3.7.3
|
Release files / automated_accessibility_testing-1.0.1-py3-none-any.whl
| Download URL | automated_accessibility_testing-1.0.1-py3-none-any.whl |
|---|---|
| Size | 17.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5f48c5869738873df69d7cb04f7e40db6a8ff9f036066cab7828070bac385325
|
|
BLAKE2b-256 checksum How to use checksums |
e70b8ccf490f9be719948f29e69eccff7a48e1cb4dfa4c874b6d2391426facd1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.25.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.54.1 CPython/3.7.3
|
Security for automated-accessibility-testing 1.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.