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

[achecker] local 1.3 running with uploaded file: internet active/not active different results #77

Open
lamu84 opened this issue Mar 9, 2018 · 3 comments

Comments

@lamu84
Copy link

lamu84 commented Mar 9, 2018

Hi,
I ran some files with local achecker 1.3, php version 5.3.0.(attached one for testing).
i tried uploading file with internet connection active and not active, and giving local url to file with internet connection active and not active.
Achecker returns me 0 html validation problems when connection internet is down, returns correctly html error(12) when internet connection is active.
Giving local url achecker returns me warning like( file get contents()(http://validator.w3.org/check?uri=http://127.0.0.1/SOLOHTML/058029.html): failed to open stream:php network getaddresses:getaddrinfo failed
So I ask you if achecker needs internet connection active to connect to the w3c validator, also when i use local achecker 1.3
Because seems to me it needs internet conncetion active to connect to the w3c validator for html validation, otherwise returns 0 html validation.
Do you confirm that local achecker works like I said?
Also change known problems and potential when local achecker 1.3 runs with internet connection active or down.
namefile uploaded:058029
local achecker 1.3with internet active
Known Problems(93)Likely Problems (23)Potential Problems (409)HTML Validation (12)
local achecker 1.3 with internet not active
Known Problems(65) Likely Problems (23)Potential Problems (472) HTML Validation (0)
Is it all expected or is it a bug?
Sorry for so many questions.
Thanks.
058029.zip

@cindyli
Copy link
Contributor

cindyli commented Mar 9, 2018

You are welcome to report problems, @lamu84.

AChecker does require internet connection for html validation. The main goal of AChecker is to perform accessibility validation. It uses APIs provided by W3C validator for html validation to make it more convenient for users.

My test result of validating the attached html with my local achecker:
With internet: 52 known problems, 23 likely problems, 409 potential problems;
Without internet: 51 known problems, 23 likely problems, 472 potential problems.

It's reasonable that more potential problems are reported when there is no internet connection because AChecker fetches remote images to evaluate size etc, and remote css to evaluate colors etc when needed. But what is interesting is that the known problem becomes less when disconnected from internet.

I created a bug report for a future investigation: http://www.atutor.ca/atutor/mantis/view.php?id=5852

@lamu84
Copy link
Author

lamu84 commented Mar 10, 2018

Thank you for your answer. Please check also (with same files html) known and likely problems numbers, with local version 1.3 and on line https://achecker.ca/checker/index.php
because with many files achecker on line and local achecker returns different numbers of likely and known.
i attached for examples two export csv file reporting different known problems for the same file used both with local and https://achecker.ca/
achecker_2018-03-09_12-35-44.zip
012133.zip

@lamu84
Copy link
Author

lamu84 commented Mar 10, 2018

probably the bug for differents likely results with https://achecker.ca/likely ands local is that check n.3 in local is reported as a potential problems and not as a likely.
in the guideline check n. 3 is a likely: https://achecker.ca/guideline/view_guideline.php?id=8

maybe there are others problems like this.

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

2 participants