Skip to content
This repository has been archived by the owner on Apr 30, 2021. It is now read-only.

[Achecker]different result browser Chrome and Mozilla #75

Open
lamu84 opened this issue Mar 8, 2018 · 2 comments
Open

[Achecker]different result browser Chrome and Mozilla #75

lamu84 opened this issue Mar 8, 2018 · 2 comments

Comments

@lamu84
Copy link

lamu84 commented Mar 8, 2018

Hi,
Using these two browsers(mozilla and chrome) https://achecker.ca/checker/index.php returns me different result for likely and potential problems, for the same file uploaded.
Wcag 2.0 (AA)
Mozilla returns :0 known, 1 likely, 405 potential
Chrome return: 0 known, 0 likely, 243 potential
Shoulden't be always the same problems, also with different browser?
Running in local achecker returns me: 0 known, 0 likely , 243 potential errors.
061025.zip
Thank you again.

@cindyli
Copy link
Contributor

cindyli commented Mar 8, 2018

With achecker.ca in my experiment by uploading the attached html file, these two browsers return same number of problems: 0 known, 1 likely, 405 potential

@ushukkla
Copy link

While browscap.ini contains information on many browsers, it relies on user updates to keep the database current. The format of the file is fairly self-explanatory. So, this may vary user to user and browser to browser.
Else follow the code given.
echo $_SERVER['HTTP_USER_AGENT'] . "\n\n";

$browser = get_browser(null, true);
print_r($browser);

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants