www.htmlyse.com - Home

Test DNS, SSL/TLS, HTTP and HTML

Test results for w3.org

Scanned on: Wed Jul 25 16:36:30 2018 GMT. Tested in 354 seconds

DNS Report

DNSSEC                 not offered
Zone transfer (AXFR)   not allowed (OK)
CAA Record             offered (OK)
SPF Record             offered (OK)
DMARC Record           not offered
MTA-STS                not offered
TLSRPT Record          not offered

Raw DNS Records

Name TTL Type Data
w3.org 3600 SOA ns1.w3.org hostmaster @ w3.org 2018071801 28800 3600 604800 1800
w3.org 3600 NS ns1.w3.org, IPv4: 128.30.52.200, IPv6: 2603:400a:ffff:804:801e:34:0:c8
w3.org 3600 NS ns2.w3.org, IPv4: 128.30.52.201, IPv6: 2603:400a:ffff:804:801e:34:0:c9
w3.org 3600 NS ns3.w3.org, IPv4: 193.51.208.66
w3.org 3600 A 128.30.52.45
w3.org 3600 AAAA 2603:400a:ffff:804:801e:34:0:2d
w3.org 3600 CAA 0 iodef mailto : web-human @ w3.org
w3.org 3600 CAA 0 issuewild comodoca.com
w3.org 3600 CAA 0 issue letsencrypt.org
w3.org 3600 MX 10 mimas.w3.org
w3.org 3600 MX 10 titan.w3.org
w3.org 3600 MX 50 bart.w3.org
w3.org 3600 TXT v=spf1 a mx ptr ip4:128.30.52.0/22 ip4:203.178.154.0/25 ip4:193.51.208.64/27 include:spf6.w3.org include:spf.braintreegateway.com ~all
www.w3.org 900 A 128.30.52.100

SSL/TLS Report

 Further IP addresses:   2603:400a:ffff:804:801e:34:0:2d 
 A record via            supplied IP "128.30.52.45"
 rDNS (128.30.52.45):    dolph.w3.org.
 Service detected:       HTTP


 SSL/TLS protocols 
 SSLv2      not offered (OK)
 SSLv3      not offered (OK)
 TLS 1      offered
 TLS 1.1    offered
 TLS 1.2    offered (OK)
 TLS 1.3    not offered -- downgraded
 NPN/SPDY   h2, http/1.1 (advertised)
 ALPN/HTTP2 h2, http/1.1 (offered)

 SSL/TLS server implementation bugs 

 No bugs found.

 Cipher categories 

 NULL ciphers (no encryption)                  not offered (OK) -- NULL:eNULL
 Anonymous NULL Ciphers (no authentication)    not offered (OK) -- aNULL:ADH
 Export ciphers (w/o ADH+NULL)                 not offered (OK) -- EXPORT:!ADH:!NULL
 LOW: 64 Bit + DES encryption (w/o export)     not offered (OK) -- LOW:DES:!ADH:!EXP:!NULL
 Weak 128 Bit ciphers (SEED, IDEA, RC[2,4])    not offered (OK) -- MEDIUM:!aNULL:!AES:!CAMELLIA:!ARIA:!CHACHA20:!3DES
 Triple DES Ciphers (Medium)                   not offered (OK) -- 3DES:!aNULL:!ADH
 High encryption (AES+Camellia, no AEAD)       offered (OK) -- HIGH:!NULL:!aNULL:!DES:!3DES:!AESGCM:!CHACHA20:!AESGCM:!CamelliaGCM:!AESCCM8:!AESCCM
 Strong encryption (AEAD ciphers)              offered (OK) -- AESGCM:CHACHA20:AESGCM:CamelliaGCM:AESCCM8:AESCCM


 Robust (perfect) forward secrecy, (P)FS -- omitting Null Authentication/Encryption, 3DES, RC4 

 PFS is offered (OK)          ECDHE-RSA-AES256-GCM-SHA384 
                              ECDHE-RSA-AES256-SHA384 ECDHE-RSA-AES256-SHA 
                              ECDHE-RSA-CHACHA20-POLY1305 
                              ECDHE-RSA-CAMELLIA256-SHA384 
                              ECDHE-RSA-AES128-GCM-SHA256 
                              ECDHE-RSA-AES128-SHA256 ECDHE-RSA-AES128-SHA 
                              ECDHE-RSA-CAMELLIA128-SHA256 
 Elliptic curves offered:     prime256v1 


 Server preferences 

 Has server cipher order?     yes (OK)
 Negotiated protocol          TLSv1.2
 Negotiated cipher            ECDHE-RSA-AES256-GCM-SHA384, 256 bit ECDH (P-256)
 Cipher order
    TLSv1:     ECDHE-RSA-AES256-SHA ECDHE-RSA-AES128-SHA AES256-SHA 
               CAMELLIA256-SHA AES128-SHA CAMELLIA128-SHA 
    TLSv1.1:   ECDHE-RSA-AES256-SHA ECDHE-RSA-AES128-SHA AES256-SHA 
               CAMELLIA256-SHA AES128-SHA CAMELLIA128-SHA 
    TLSv1.2:   ECDHE-RSA-AES256-GCM-SHA384 ECDHE-RSA-CHACHA20-POLY1305 
               ECDHE-RSA-AES128-GCM-SHA256 ECDHE-RSA-AES256-SHA384 
               ECDHE-RSA-CAMELLIA256-SHA384 ECDHE-RSA-AES128-SHA256 
               ECDHE-RSA-CAMELLIA128-SHA256 ECDHE-RSA-AES256-SHA 
               ECDHE-RSA-AES128-SHA AES256-GCM-SHA384 AES256-CCM8 AES256-CCM 
               AES128-GCM-SHA256 AES128-CCM8 AES128-CCM AES256-SHA256 
               CAMELLIA256-SHA256 AES128-SHA256 CAMELLIA128-SHA256 AES256-SHA 
               CAMELLIA256-SHA AES128-SHA CAMELLIA128-SHA 


 Server defaults (Server Hello) 

 TLS extensions (standard)    "renegotiation info/#65281" "server name/#0"
                              "EC point formats/#11" "session ticket/#35"
                              "status request/#5" "next protocol/#13172"
                              "encrypt-then-mac/#22"
                              "extended master secret/#23"
                              "application layer protocol negotiation/#16"
 Session Ticket RFC 5077 hint 7200 seconds, session tickets keys seems to be rotated < daily
 SSL Session ID support       yes
 Session Resumption           Tickets: yes, ID: yes
 TLS clock skew               Random values, no fingerprinting possible 
 Signature Algorithm          SHA256 with RSA
 Server key size              RSA 2048 bits
 Server key usage             Digital Signature, Key Encipherment
 Server extended key usage    TLS Web Server Authentication, TLS Web Client Authentication
 Serial / Fingerprints        31CE07E8897EA656083C8CAEE6D2C84E / SHA1 5ACFFEF0F1A6F45FD21111C61D2F0EBC398D50E0
                              SHA256 4D91B863CB3C1C9D53599AC0993A65EC5957AC3A425802A254B65981F7B64567
 Common Name (CN)             *.w3.org
 subjectAltName (SAN)         *.w3.org w3.org 
 Issuer                       Gandi Standard SSL CA 2 (Gandi from FR)
 Trust (hostname)             Ok via SAN (same w/o SNI)
 Chain of trust               Ok   
 EV cert (experimental)       no 
 Certificate Validity (UTC)   311 >= 60 days (2017-05-02 02:00 --> 2019-06-02 01:59)
 # of certificates provided   3
 Certificate Revocation List  http://crl.usertrust.com/GandiStandardSSLCA2.crl
 OCSP URI                     http://ocsp.usertrust.com
 OCSP stapling                offered
 OCSP must staple extension   --
 DNS CAA RR (experimental)    available - please check for match with "Issuer" above
                              iodef=mailto:web-human@w3.org,
                              issue=letsencrypt.org, issuewild=comodoca.com
 Certificate Transparency     --


 HTTP header response @ "/" 

 HTTP Status Code             301 Moved Permanently, redirecting to "https://www.w3.org/"
 HTTP clock skew              Got no HTTP time, maybe try different URL?
 Strict Transport Security    not offered
 Public Key Pinning           --
 Server banner                (no "Server" line in header, interesting!)
 Application banner           --
 Cookie(s)                    (none issued at "/") -- maybe better try target URL of 30x
 Security headers             --
 Reverse Proxy banner         --


 SSL/TLS vulnerabilities 

 Heartbleed (CVE-2014-0160)                not vulnerable (OK), no heartbeat extension
 CCS (CVE-2014-0224)                       not vulnerable (OK)
 Ticketbleed (CVE-2016-9244), experiment.  not vulnerable (OK)
 ROBOT                                     not vulnerable (OK)
 Secure Renegotiation (CVE-2009-3555)      not vulnerable (OK)
 Secure Client-Initiated Renegotiation     not vulnerable (OK)
 CRIME, TLS (CVE-2012-4929)                not vulnerable (OK)
 BREACH (CVE-2013-3587)                    no HTTP compression (OK)  - only supplied "/" tested
 POODLE, SSL (CVE-2014-3566)               not vulnerable (OK)
 TLS_FALLBACK_SCSV (RFC 7507)              Downgrade attack prevention supported (OK)
 SWEET32 (CVE-2016-2183, CVE-2016-6329)    not vulnerable (OK)
 FREAK (CVE-2015-0204)                     not vulnerable (OK)
 DROWN (CVE-2016-0800, CVE-2016-0703)      not vulnerable on this host and port (OK)
                                           make sure you don't use this certificate elsewhere with SSLv2 enabled services
                                           https://censys.io/ipv4?q=4D91B863CB3C1C9D53599AC0993A65EC5957AC3A425802A254B65981F7B64567
                                           could help you to find out
 LOGJAM (CVE-2015-4000), experimental      not vulnerable (OK): no DH EXPORT ciphers, no DH key detected
 BEAST (CVE-2011-3389)                     TLS1: ECDHE-RSA-AES256-SHA
                                                 ECDHE-RSA-AES128-SHA
                                                 AES256-SHA CAMELLIA256-SHA
                                                 AES128-SHA CAMELLIA128-SHA 
                                           VULNERABLE -- but also supports higher protocols  TLSv1.1 TLSv1.2 (likely mitigated)
 LUCKY13 (CVE-2013-0169), experimental     potentially VULNERABLE, uses cipher block chaining (CBC) ciphers with TLS. Check patches
 RC4 (CVE-2013-2566, CVE-2015-2808)        no RC4 ciphers detected (OK)


 Tested 364 ciphers, ordered by encryption strength 

Hexcode  Cipher Suite Name (OpenSSL)       KeyExch.   Encryption  Bits     Cipher Suite Name (RFC)
-----------------------------------------------------------------------------------------------------------------------------
 xc030   ECDHE-RSA-AES256-GCM-SHA384       ECDH 256   AESGCM      256      TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384              
 xc028   ECDHE-RSA-AES256-SHA384           ECDH 256   AES         256      TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384              
 xc014   ECDHE-RSA-AES256-SHA              ECDH 256   AES         256      TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA                 
 xcca8   ECDHE-RSA-CHACHA20-POLY1305       ECDH 256   ChaCha20    256      TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256        
 xc077   ECDHE-RSA-CAMELLIA256-SHA384      ECDH 256   Camellia    256      TLS_ECDHE_RSA_WITH_CAMELLIA_256_CBC_SHA384         
 x9d     AES256-GCM-SHA384                 RSA        AESGCM      256      TLS_RSA_WITH_AES_256_GCM_SHA384                    
 xc0a1   AES256-CCM8                       RSA        AESCCM8     256      TLS_RSA_WITH_AES_256_CCM_8                         
 xc09d   AES256-CCM                        RSA        AESCCM      256      TLS_RSA_WITH_AES_256_CCM                           
 x3d     AES256-SHA256                     RSA        AES         256      TLS_RSA_WITH_AES_256_CBC_SHA256                    
 x35     AES256-SHA                        RSA        AES         256      TLS_RSA_WITH_AES_256_CBC_SHA                       
 xc0     CAMELLIA256-SHA256                RSA        Camellia    256      TLS_RSA_WITH_CAMELLIA_256_CBC_SHA256               
 x84     CAMELLIA256-SHA                   RSA        Camellia    256      TLS_RSA_WITH_CAMELLIA_256_CBC_SHA                  
 xc02f   ECDHE-RSA-AES128-GCM-SHA256       ECDH 256   AESGCM      128      TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256              
 xc027   ECDHE-RSA-AES128-SHA256           ECDH 256   AES         128      TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256              
 xc013   ECDHE-RSA-AES128-SHA              ECDH 256   AES         128      TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA                 
 xc0a0   AES128-CCM8                       RSA        AESCCM8     128      TLS_RSA_WITH_AES_128_CCM_8                         
 xc09c   AES128-CCM                        RSA        AESCCM      128      TLS_RSA_WITH_AES_128_CCM                           
 xc076   ECDHE-RSA-CAMELLIA128-SHA256      ECDH 256   Camellia    128      TLS_ECDHE_RSA_WITH_CAMELLIA_128_CBC_SHA256         
 x9c     AES128-GCM-SHA256                 RSA        AESGCM      128      TLS_RSA_WITH_AES_128_GCM_SHA256                    
 x3c     AES128-SHA256                     RSA        AES         128      TLS_RSA_WITH_AES_128_CBC_SHA256                    
 x2f     AES128-SHA                        RSA        AES         128      TLS_RSA_WITH_AES_128_CBC_SHA                       
 xba     CAMELLIA128-SHA256                RSA        Camellia    128      TLS_RSA_WITH_CAMELLIA_128_CBC_SHA256               
 x41     CAMELLIA128-SHA                   RSA        Camellia    128      TLS_RSA_WITH_CAMELLIA_128_CBC_SHA                  


 Ciphers per protocol, ordered by encryption strength 

Hexcode  Cipher Suite Name (OpenSSL)       KeyExch.   Encryption  Bits     Cipher Suite Name (RFC)
-----------------------------------------------------------------------------------------------------------------------------
TLS 1.3  
TLS 1.2  
 xc030   ECDHE-RSA-AES256-GCM-SHA384       ECDH 256   AESGCM      256      TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384              
 xc028   ECDHE-RSA-AES256-SHA384           ECDH 256   AES         256      TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384              
 xc014   ECDHE-RSA-AES256-SHA              ECDH 256   AES         256      TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA                 
 xcca8   ECDHE-RSA-CHACHA20-POLY1305       ECDH 256   ChaCha20    256      TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256        
 xc077   ECDHE-RSA-CAMELLIA256-SHA384      ECDH 256   Camellia    256      TLS_ECDHE_RSA_WITH_CAMELLIA_256_CBC_SHA384         
 x9d     AES256-GCM-SHA384                 RSA        AESGCM      256      TLS_RSA_WITH_AES_256_GCM_SHA384                    
 xc0a1   AES256-CCM8                       RSA        AESCCM8     256      TLS_RSA_WITH_AES_256_CCM_8                         
 xc09d   AES256-CCM                        RSA        AESCCM      256      TLS_RSA_WITH_AES_256_CCM                           
 x3d     AES256-SHA256                     RSA        AES         256      TLS_RSA_WITH_AES_256_CBC_SHA256                    
 x35     AES256-SHA                        RSA        AES         256      TLS_RSA_WITH_AES_256_CBC_SHA                       
 xc0     CAMELLIA256-SHA256                RSA        Camellia    256      TLS_RSA_WITH_CAMELLIA_256_CBC_SHA256               
 x84     CAMELLIA256-SHA                   RSA        Camellia    256      TLS_RSA_WITH_CAMELLIA_256_CBC_SHA                  
 xc02f   ECDHE-RSA-AES128-GCM-SHA256       ECDH 256   AESGCM      128      TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256              
 xc027   ECDHE-RSA-AES128-SHA256           ECDH 256   AES         128      TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256              
 xc013   ECDHE-RSA-AES128-SHA              ECDH 256   AES         128      TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA                 
 xc0a0   AES128-CCM8                       RSA        AESCCM8     128      TLS_RSA_WITH_AES_128_CCM_8                         
 xc09c   AES128-CCM                        RSA        AESCCM      128      TLS_RSA_WITH_AES_128_CCM                           
 xc076   ECDHE-RSA-CAMELLIA128-SHA256      ECDH 256   Camellia    128      TLS_ECDHE_RSA_WITH_CAMELLIA_128_CBC_SHA256         
 x9c     AES128-GCM-SHA256                 RSA        AESGCM      128      TLS_RSA_WITH_AES_128_GCM_SHA256                    
 x3c     AES128-SHA256                     RSA        AES         128      TLS_RSA_WITH_AES_128_CBC_SHA256                    
 x2f     AES128-SHA                        RSA        AES         128      TLS_RSA_WITH_AES_128_CBC_SHA                       
 xba     CAMELLIA128-SHA256                RSA        Camellia    128      TLS_RSA_WITH_CAMELLIA_128_CBC_SHA256               
 x41     CAMELLIA128-SHA                   RSA        Camellia    128      TLS_RSA_WITH_CAMELLIA_128_CBC_SHA                  
TLS 1.1  
 xc014   ECDHE-RSA-AES256-SHA              ECDH 256   AES         256      TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA                 
 x35     AES256-SHA                        RSA        AES         256      TLS_RSA_WITH_AES_256_CBC_SHA                       
 x84     CAMELLIA256-SHA                   RSA        Camellia    256      TLS_RSA_WITH_CAMELLIA_256_CBC_SHA                  
 xc013   ECDHE-RSA-AES128-SHA              ECDH 256   AES         128      TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA                 
 x2f     AES128-SHA                        RSA        AES         128      TLS_RSA_WITH_AES_128_CBC_SHA                       
 x41     CAMELLIA128-SHA                   RSA        Camellia    128      TLS_RSA_WITH_CAMELLIA_128_CBC_SHA                  
TLS 1  
 xc014   ECDHE-RSA-AES256-SHA              ECDH 256   AES         256      TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA                 
 x35     AES256-SHA                        RSA        AES         256      TLS_RSA_WITH_AES_256_CBC_SHA                       
 x84     CAMELLIA256-SHA                   RSA        Camellia    256      TLS_RSA_WITH_CAMELLIA_256_CBC_SHA                  
 xc013   ECDHE-RSA-AES128-SHA              ECDH 256   AES         128      TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA                 
 x2f     AES128-SHA                        RSA        AES         128      TLS_RSA_WITH_AES_128_CBC_SHA                       
 x41     CAMELLIA128-SHA                   RSA        Camellia    128      TLS_RSA_WITH_CAMELLIA_128_CBC_SHA                  
SSLv3  
SSLv2  

 Client simulations 

 Android 4.2.2                TLSv1.0 ECDHE-RSA-AES256-SHA, 256 bit ECDH (P-256)
 Android 4.4.2                TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 256 bit ECDH (P-256)
 Android 5.0.0                TLSv1.2 ECDHE-RSA-AES128-GCM-SHA256, 256 bit ECDH (P-256)
 Android 6.0                  TLSv1.2 ECDHE-RSA-AES128-GCM-SHA256, 256 bit ECDH (P-256)
 Android 7.0                  TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 256 bit ECDH (P-256)
 Chrome 57 Win 7              TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 256 bit ECDH (P-256)
 Chrome 65 Win 7              TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 256 bit ECDH (P-256)
 Firefox 53 Win 7             TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 256 bit ECDH (P-256)
 Firefox 59 Win 7             TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 256 bit ECDH (P-256)
 IE 6 XP                      No connection
 IE 7 Vista                   TLSv1.0 ECDHE-RSA-AES256-SHA, 256 bit ECDH (P-256)
 IE 8 Win 7                   TLSv1.0 ECDHE-RSA-AES256-SHA, 256 bit ECDH (P-256)
 IE 8 XP                      No connection
 IE 11 Win 7                  TLSv1.2 ECDHE-RSA-AES256-SHA384, 256 bit ECDH (P-256)
 IE 11 Win 8.1                TLSv1.2 ECDHE-RSA-AES256-SHA384, 256 bit ECDH (P-256)
 IE 11 Win Phone 8.1          TLSv1.2 ECDHE-RSA-AES128-SHA256, 256 bit ECDH (P-256)
 IE 11 Win 10                 TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 256 bit ECDH (P-256)
 Edge 13 Win 10               TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 256 bit ECDH (P-256)
 Edge 13 Win Phone 10         TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 256 bit ECDH (P-256)
 Edge 15 Win 10               TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 256 bit ECDH (P-256)
 Opera 17 Win 7               TLSv1.2 ECDHE-RSA-AES128-SHA256, 256 bit ECDH (P-256)
 Safari 9 iOS 9               TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 256 bit ECDH (P-256)
 Safari 9 OS X 10.11          TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 256 bit ECDH (P-256)
 Safari 10 OS X 10.12         TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 256 bit ECDH (P-256)
 Apple ATS 9 iOS 9            TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 256 bit ECDH (P-256)
 Tor 17.0.9 Win 7             TLSv1.0 ECDHE-RSA-AES256-SHA, 256 bit ECDH (P-256)
 Java 6u45                    TLSv1.0 AES128-SHA
 Java 7u25                    TLSv1.0 ECDHE-RSA-AES128-SHA, 256 bit ECDH (P-256)
 Java 8u161                   TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 256 bit ECDH (P-256)
 Java 9.0.4                   TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 256 bit ECDH (P-256)
 OpenSSL 1.0.1l               TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 256 bit ECDH (P-256)
 OpenSSL 1.0.2e               TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 256 bit ECDH (P-256)


Security HTTP Headers

HTTP Strict Transport Security (HSTS)   offered (OK)
Content Security Policy (CSP)           offered (OK)
X-Frame-Options                         not offered (NOT ok)
X-XSS-Protection                        not offered
X-Content-Type-Options                  not offered
Expect-CT                               not offered
Referrer Policy                         not offered
Feature Policy                          not offered
Web Server Version Disclosure           not offered (OK)
Web Application Disclosure              not offered (OK)
HTTP Public Key Pins (HPKP)             not offered, deprecated

Connection Performance
Keep Alive Connection                   not offered
Content Encoding (Compression)          offered (Gzip) OK, for static pages or if no secrets in the page

Raw HTTP Headers

HTTP/1.1 200 OK
Accept-Ranges bytes
Cache-Control max-age=600
Content-Encoding gzip
Content-Length 10268
Content-Location Home.html
Content-Security-Policy upgrade-insecure-requests
Content-Type text/html; charset=utf-8
Date Wed, 25 Jul 2018 16:30:46 GMT
ETag "9b7e-571b135f5bb00;89-3f26bd17a2f00-gzip"
Expires Wed, 25 Jul 2018 16:40:46 GMT
Last-Modified Mon, 23 Jul 2018 21:20:12 GMT
P3P policyref="http://www.w3.org/2014/08/p3p.xml"
Strict-Transport-Security max-age=15552000; includeSubdomains; preload
TCN choice
Vary negotiate,accept,Accept-Encoding

Cleaned HTML

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN">
<html lang="en">
<head>
<title>World Wide Web Consortium (W3C)</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<link rel="Help" href="/Help/">
<link rel="stylesheet" href="/2008/site/css/minimum" type="text/css" media="all">
<style type="text/css" media="print, screen and (min-width: 481px)">
/*<![CDATA[*/
@import url("/2008/site/css/advanced");
/*]]>*/
</style>
<link href="/2008/site/css/minimum" rel="stylesheet" type="text/css" media="only screen and (max-width: 480px)">
<meta name="viewport" content="width=device-width">
<link rel="stylesheet" href="/2008/site/css/print" type="text/css" media="print">
<link rel="shortcut icon" href="/2008/site/images/favicon.ico" type="image/x-icon">
<meta name="description" content="The World Wide Web Consortium (W3C) is an international community where Member organizations, a full-time staff, and the public work together to develop Web standards.">
<link rel="alternate" type="application/atom+xml" title="W3C News" href="/blog/news/feed/atom">
<style type="text/css">
p.c1 {text-align: center}
</style>
</head>
<body id="www-w3-org" class="w3c_public w3c_home">
<div id="w3c_container">
<div id="w3c_mast">
<h1 class="logo"><a tabindex="2" accesskey="1" href="/"><img src="/2008/site/images/logo-w3c-mobile-lg" width="90" height="53" alt="W3C"></a> <span class="alt-logo">W3C</span></h1>
<div id="w3c_nav">
<form id="region_form" action="http://www.w3.org/Consortium/contact">
<div><select name="region">
<option selected="selected" title="Get Information about W3C By Region">W3C By Region</option>
<option value="all">All</option>
<option value="au">Australia</option>
<option lang="de" value="de">Österreich (Austria)</option>
<option lang="nl" value="nl">België (Belgium)</option>
<option value="za">Botswana</option>
<option value="br" lang="pt-br">Brasil (Brazil)</option>
<option value="cn" lang="zh-hans">中国 (China)</option>
<option value="fi" lang="fi">Suomi (Finland)</option>
<option value="de" lang="de">Deutschland (Germany)</option>
<option value="gr" lang="el">Ελλάδα (Greece)</option>
<option value="fr" lang="fr">France</option>
<option value="hu" lang="hu">Magyarország (Hungary)</option>
<option value="in" lang="hi">भारत (India)</option>
<option lang="ga" value="gb">Éire (Ireland)</option>
<option value="il" lang="he">ישראל (Israel)</option>
<option value="it" lang="it">Italia (Italy)</option>
<option value="jp" lang="ja">日本 (Japan)</option>
<option value="kr" lang="ko">한국 (Korea)</option>
<option value="za">Lesotho</option>
<option lang="lb" value="nl">Lëtzebuerg (Luxembourg)</option>
<option value="ma" lang="ar">المغرب (Morocco)</option>
<option value="za">Namibia</option>
<option lang="nl" value="nl">Nederland (Netherlands)</option>
<option value="ru" lang="ru">Россия (Russia)</option>
<option value="sn" lang="fr">Sénégal</option>
<option value="es" lang="es">España (Spain)</option>
<option value="za">South Africa</option>
<option lang="ss" value="za">Swatini (Swaziland)</option>
<option value="se" lang="sv">Sverige (Sweden)</option>
<option value="gb">United Kingdom</option>
</select> <input class="button" type="submit" value="Go"></div>
</form>
<form action="https://www.w3.org/Help/search" method="get" enctype="application/x-www-form-urlencoded">
<div class="w3c_sec_nav"></div>
<ul class="main_nav">
<li class="first-item"><a href="/standards/">Standards</a></li>
<li><a href="/participate/">Participate</a></li>
<li><a href="/Consortium/membership">Membership</a></li>
<li class="last-item"><a href="/Consortium/">About W3C</a></li>
<li class="search-item">
<div id="search-form"><input tabindex="3" class="text" name="q" value="" title="Search"> <button id="search-submit" name="search-submit" type="submit"><img class="submit" src="/2008/site/images/search-button" alt="Search" width="21" height="17"></button></div>
</li>
</ul>
</form>
</div>
</div>
<div id="w3c_main">
<div id="w3c_logo_shadow" class="w3c_leftCol"><img height="32" alt="" src="/2008/site/images/logo-shadow"></div>
<div class="w3c_leftCol">
<h2 class="offscreen">Site Navigation</h2>
<h3 class="category"><span class="ribbon"><a title="All Standards and Drafts from W3C" href="/TR/">Technical Reports <img src="/2008/site/images/header-link.gif" alt="Header link" width="13" height="13" class="header-link"></a></span></h3>
<h3 class="category tMargin"><span class="ribbon"><a href="standards">Web and Industry <img src="/2008/site/images/header-link.gif" alt="Header link" width="13" height="13" class="header-link"></a></span></h3>
<ul class="theme">
<li><a href="auto/">Automotive</a></li>
<li><a href="tv/">Entertainment (TV and Broadcasting)</a></li>
<li><a href="publishing/">Publishing</a></li>
<li><a href="WebCommerce/">Web Commerce</a></li>
<li><a href="2013/data/">Web of Data</a></li>
<li><a href="Payments/WG/">Web Payments</a></li>
<li><a href="Telco/">Web and Telecommunications</a></li>
<li><a href="WoT/">Web of Things</a></li>
<li><a href="Security">Web Security</a></li>
</ul>
<h3 class="category tMargin"><span class="ribbon"><a href="Consortium/mission.html#principles">Web for All <img src="/2008/site/images/header-link.gif" alt="Header link" width="13" height="13" class="header-link"></a></span></h3>
<ul class="theme">
<li><a href="/WAI/">Accessibility</a></li>
<li><a href="/International/">Internationalization</a></li>
<li><a title="Popular links to W3C technology information" href="Consortium/siteindex.html#technologies">W3C A&nbsp;to&nbsp;Z</a></li>
</ul>
<h3 class="category tMargin"><span class="ribbon"><a href="/community/">Community and Business Groups <img src="/2008/site/images/header-link.gif" alt="Header link" width="13" height="13" class="header-link"></a></span></h3>
<ul class="theme">
<li><a href="/community/groups/">Current Groups</a></li>
<li><a href="/community/groups/proposed/">Proposed Groups</a></li>
</ul>
<h3 class="category tMargin"><span class="ribbon"><a href="Consortium/activities">Working Groups <img src="/2008/site/images/header-link.gif" alt="Header link" width="13" height="13" class="header-link"></a></span></h3>
<ul class="theme">
<li><a href="/Consortium/activities">W3C Groups</a></li>
<li><a title="Member-only group participant guidebook" href="/Guide/">Participant guidebook</a></li>
</ul>
<h3 class="category tMargin"><span class="ribbon"><a href="participate/">Dev Resources <img src="/2008/site/images/header-link.gif" alt="Header link" width="13" height="13" class="header-link"></a></span></h3>
<ul class="theme">
<li><a title="Open Web Platform testing" href="http://web-platform-tests.org/">Web Platform Tests</a></li>
<li><a title="W3C Developer Avenue" href="/developers/"><img src="/2015/10/W3C-Developers_Assets/W3C-Developers-Dark.png" width="150" alt="W3C Developers"></a></li>
<li><a title="MOOCs from W3C on edX" href="https://www.edx.org/school/w3cx"><img src="/2015/04/w3cx-home.png" alt="W3Cx"></a></li>
<li><a href="participate/">More ways to participate</a></li>
</ul>
<h3 class="category tMargin"><span class="ribbon"><a href="/Member/">Member-only Home <img src="/2008/site/images/header-link.gif" alt="Header link" width="13" height="13" class="header-link"></a></span></h3>
<ul class="theme">
<li><a href="http://www.w3.org/Consortium/activities">Join a Group</a></li>
<li><a href="http://www.w3.org/Help/Account/Request/Member">Get Member Account</a></li>
</ul>
</div>
<div class="w3c_mainCol">
<div id="w3c_crumbs">
<div id="w3c_crumbs_frame">
<p class="bct"><span class="skip"><a tabindex="1" accesskey="2" title="Skip to content (e.g., when browsing via audio)" href="#w3c_most-recently">Skip</a></span></p>
<br></div>
</div>
<div class="line">
<div class="unit size2on3">
<div class="main-content">
<h2 class="offscreen">News</h2>
<div id="w3c_slideshow">
<div id="w3c_most-recently" class="intro hierarchy vevent_list">
<div class="event w3c_topstory expand_block">
<div class="headline">
<h3 class="h4 tPadding0 bPadding0 summary"><span class="expand_section">W3C launches Internationalization Initiative</span></h3>
<p class="date"><span class="dtstart published" title="2018-07-09T06:08:42Z">9 July 2018</span> | <a title="Archive: W3C launches Internationalization Initiative" href="https://www.w3.org/blog/news/archives/7156">Archive</a></p>
</div>
<div class="description expand_description">
<p><a class="imageLink" href="https://www.w3.org/2018/07/pressrelease-i18n-initiative.html.en"><img src="https://www.w3.org/International/icons/sitetitle.gif" alt="Internationalization (I18n) Activity: Making the World Wide Web truly world wide!" width="100"></a>The World Wide Web Consortium today launched the Internationalization Initiative to expand core work in further internationalizing the Web. “Supporting the W3C Internationalization Initiative with funding or expertise is a vital way that our Web community creates the future of the global Web,” said Jeff Jaffe, W3C CEO. W3C thanks Alibaba, Apple, Advanced Publishing Lab (Keio University), Monotype, and The Paciello Group who have stepped up as Founding Sponsors. Read about <a href="https://www.w3.org/International/sponsorship/">W3C Internationalization and its Sponsorship Program</a> and the <a href="https://www.w3.org/2018/07/pressrelease-i18n-initiative.html.en">press release and testimonials</a>.</p>
</div>
</div>
<div class="event closed expand_block">
<div class="headline">
<h3 class="h4 tPadding0 bPadding0 summary"><span class="expand_section">First Public Working Drafts: WAI-ARIA 1.2, Core-AAM 1.2, and ARIA Practices 1.2</span></h3>
<p class="date"><span class="dtstart published" title="2018-07-19T12:28:24Z">19 July 2018</span> | <a title="Archive: First Public Working Drafts: WAI-ARIA 1.2, Core-AAM 1.2, and ARIA Practices 1.2" href="https://www.w3.org/blog/news/archives/7200">Archive</a></p>
</div>
<div class="description expand_description">
<p>The <a href="https://www.w3.org/WAI/ARIA/">Accessible Rich Internet Applications Working Group</a> has published First Public Working Drafts of <a href="https://www.w3.org/TR/2018/WD-wai-aria-1.2-20180719/">Accessible Rich Internet Applications 1.2</a> (WAI-ARIA), <a href="https://www.w3.org/TR/2018/WD-core-aam-1.2-20180719/">Core Accessibility API Mappings 1.2</a> (Core-AAM), and <a href="https://www.w3.org/TR/2018/WD-wai-aria-practices-1.2-20180719/">WAI-ARIA Authoring Practices 1.2</a> (ARIA APG). WAI-ARIA 1.2 continues development of the technology after ARIA 1.1 was completed in December 2017. This version focuses primarily on providing roles to match features of HTML, which is needed by technologies such as <a href="https://www.w3.org/standards/techs/components">Web Components</a> and <a href="http://wicg.github.io/aom/">Accessible Object Model</a>. Core-AAM 1.2 provides accessibility API mappings for these new roles, and ARIA Practices 1.2 describes recommended authoring patterns for these new roles. For more information, see the blog post <a href="https://www.w3.org/blog/2018/07/aria-1.2-fpwd/">Accessible Rich Internet Applications 1.2</a>. Read about the <a href="https://www.w3.org/WAI/ARIA/">Accessible Rich Internet Applications Working Group</a> and the <a href="http://www.w3.org/WAI/">Web Accessibility Initiative (WAI)</a>.</p>
</div>
</div>
<div class="event closed expand_block">
<div class="headline">
<h3 class="h4 tPadding0 bPadding0 summary"><span class="expand_section">W3C Workshop Report: Web5G: Aligning evolutions of network and Web technologies</span></h3>
<p class="date"><span class="dtstart published" title="2018-07-16T08:03:24Z">16 July 2018</span> | <a title="Archive: W3C Workshop Report: Web5G: Aligning evolutions of network and Web technologies" href="https://www.w3.org/blog/news/archives/7179">Archive</a></p>
</div>
<div class="description expand_description">
<p>W3C published today the <a href="https://www.w3.org/2017/11/web5g-workshop/report.html">report</a>&nbsp;of the <a href="https://www.w3.org/2017/11/web5g-workshop/">W3C Workshop on Web5G: Aligning evolutions of network and Web technologies</a>, which was held on 10-11 May 2018, in London.</p>
<p>The report contains a summary of each session with links to the presentation slides. More detailed meeting minutes are also available<sup>[<a href="https://www.w3.org/2018/05/10-web5g-minutes.html">1</a>][<a href="https://www.w3.org/2018/05/11-web5g-minutes.html">2</a>]</sup>.</p>
<p>Network Operators, vendors, application developers, content provider and standard makers participated in this event which was designed to explore how the Open Web Platform could help drive the adoption of 5G innovations from the applications layer to the network level.</p>
<p>During the two days, participants reviewed opportunities that new emerging innovations and capabilities at the application layers can bring to the 5G network. The workshop concluded with the proposed creation of a task force of participants to explore how the 5G and Web communities might work in a productive and cohesive manner.</p>
<p>In particular, there was wide agreement on the benefit of developing compelling business and technical reasons and objectives to incentivize and drive a close collaboration among the W3C, 5G standard organizations (e.g. 3GPP), browser vendors, developers, equipment vendors and network operators. The goal is to create an environment conducive to the development and deployment of technologies that are supported by all the stakeholders in the ecosystem.</p>
<p>We thank our host, GSMA, and the Program Committee for making this event possible.</p>
</div>
</div>
<div class="event closed expand_block">
<div class="headline">
<h3 class="h4 tPadding0 bPadding0 summary"><span class="expand_section">Upcoming W3C Workshop on Permissions and User Consent</span></h3>
<p class="date"><span class="dtstart published" title="2018-07-12T08:01:29Z">12 July 2018</span> | <a title="Archive: Upcoming W3C Workshop on Permissions and User Consent" href="https://www.w3.org/blog/news/archives/7176">Archive</a></p>
</div>
<div class="description expand_description">
<p><a class="imageLink" href="https://www.w3.org/Privacy/permissions-ws-2018/cfp.html"><img src="https://www.w3.org/comm/assets/stock/shutterstock_609985322-500px.jpg" alt="Man pressing button on display with padlock" width="100"></a>W3C announced today a <a href="https://www.w3.org/Privacy/permissions-ws-2018/cfp.html">W3C Workshop on Permissions and User Consent</a>, September 18-19, 2018, in San Diego, California, USA. The event is hosted by Qualcomm.</p>
<p>The primary goal of the workshop is to bring together security and privacy experts, UI/UX researchers, browser vendors, mobile OS developers, API authors, Web publishers and users to address the privacy, security and usability challenges presented by a complex and overlapping variety of permissions and consent systems available for hardware sensors, device capabilities and applications on the Web.</p>
<p>The scope includes:</p>
<ul class="show_items">
<li>user consent;</li>
<li>bundling of permissions;</li>
<li>lifetime/duration of permissions;</li>
<li>permission inheritance to iframes and other embedded elements;</li>
<li>relation to same origin policy;</li>
<li>UIs and controls;</li>
<li>interaction with private browsing modes;</li>
<li>implicit permission grants;</li>
<li>progressive permission grants;</li>
<li>cross-stack permissions: how OS, browser, and web app permissions interact;</li>
<li>permission transparency;</li>
<li>relation to regulatory requirements;</li>
<li>special considerations for systems that use the browser as a pass-through</li>
<li>permissions/transparency/UI as it relates to display-less devices that connect to the Internet.</li>
</ul>
<p>For more information on the workshop, please see the <a href="https://www.w3.org/Privacy/permissions-ws-2018/cfp.html">workshop details and submission instructions</a>. Expression of Interest and position statements are due by <strong>August 17, 2018</strong>.</p>
</div>
</div>
<div class="event closed expand_block">
<div class="headline">
<h3 class="h4 tPadding0 bPadding0 summary"><span class="expand_section">W3C Invites Implementations of Payment Request API</span></h3>
<p class="date"><span class="dtstart published" title="2018-07-10T01:35:54Z">10 July 2018</span> | <a title="Archive: W3C Invites Implementations of Payment Request API" href="https://www.w3.org/blog/news/archives/7160">Archive</a></p>
</div>
<div class="description expand_description">
<p>The <a href="https://www.w3.org/Payments/WG/">Web Payments Working Group</a> invites implementations of an updated Candidate Recommendation of <a href="https://www.w3.org/TR/2018/CR-payment-request-20180709/">Payment Request API</a>. This specification standardizes an API to allow merchants (i.e. web sites selling physical or digital goods) to utilize one or more payment methods with minimal integration. User agents (e.g., browsers) facilitate the payment flow between merchant and user.</p>
</div>
</div>
<div class="event closed expand_block">
<div class="headline">
<h3 class="h4 tPadding0 bPadding0 summary"><span class="expand_section">W3C Invites Implementations of User Timing Level 2</span></h3>
<p class="date"><span class="dtstart published" title="2018-07-09T09:00:57Z">9 July 2018</span> | <a title="Archive: W3C Invites Implementations of User Timing Level 2" href="https://www.w3.org/blog/news/archives/7162">Archive</a></p>
</div>
<div class="description expand_description">
<p>The <a href="https://www.w3.org/webperf/">Web Performance Working Group</a> invites implementations of <a href="https://www.w3.org/TR/2018/CR-user-timing-2-20180709/">User Timing Level 2</a> Candidate Recommendation. This specification defines an interface to help web developers measure the performance of their applications by giving them access to high precision timestamps.</p>
</div>
</div>
<div class="event closed expand_block">
<div class="headline">
<h3 class="h4 tPadding0 bPadding0 summary"><span class="expand_section">W3C Invites Implementations of Identifiers for WebRTC Statistics API</span></h3>
<p class="date"><span class="dtstart published" title="2018-07-03T09:32:48Z">3 July 2018</span> | <a title="Archive: W3C Invites Implementations of Identifiers for WebRTC Statistics API" href="https://www.w3.org/blog/news/archives/7136">Archive</a></p>
</div>
<div class="description expand_description">
<p>The <a href="https://www.w3.org/2011/04/webrtc/">Web Real-Time Communications Working Group</a> invites implementations of <a href="https://www.w3.org/TR/2018/CR-webrtc-stats-20180703/">Identifiers for WebRTC’s Statistics API</a> Candidate Recommendation. This document defines a set of WebIDL objects that allow access to the statistical information about a RTCPeerConnection. These objects are returned from the getStats API that is specified in [<a href="https://www.w3.org/TR/2018/CR-webrtc-stats-20180703/#bib-webrtc">WEBRTC</a>].</p>
</div>
</div>
<div class="event closed expand_block">
<div class="headline">
<h3 class="h4 tPadding0 bPadding0 summary"><span class="expand_section">W3C offers Diversity Scholarships</span></h3>
<p class="date"><span class="dtstart published" title="2018-06-20T14:05:46Z">20 June 2018</span> | <a title="Archive: W3C offers Diversity Scholarships" href="https://www.w3.org/blog/news/archives/7102">Archive</a></p>
</div>
<div class="description expand_description">
<p><a class="imageLink" href="https://www.w3.org/blog/2018/06/diversity-at-w3c-launch-of-tpac-diversity-scholarship"><img src="https://www.w3.org/2018/10/TPAC/TPAC.png" alt="visual identity for TPAC 2018" width="100"></a>W3C announced today it was <a href="https://www.w3.org/2002/09/wbs/1/diversity-scholarship-application-2018/">offering Diversity Scholarships</a>. The announcement was made as part of the <a href="https://www.w3.org/blog/2018/06/diversity-at-w3c-launch-of-tpac-diversity-scholarship">publication of W3C top-level diversity statistics</a>.</p>
<p>The lack of diversity in tech is a longstanding issue. We would like W3C to be a model of supporting diversity. As an international organization we can see the immense value we gain from having expertise from across multiple countries and cultures. Soon 50% of the world will be on the Web. We know we will need to reflect the diversity of the whole of our world as more and more people begin to access, use and continue to create the Web in all its full potential.</p>
<p>During the Spring W3C Advisory Committee Meeting, a panel on diversity focused on progress we have made and how much more is required. W3C has established a modest fund for <a href="https://www.w3.org/2018/10/TPAC/">TPAC</a> Diversity Scholarships, sponsored by W3C Members <strong>Samsung Electronics</strong>, <strong>The Paciello Group</strong>, <strong>Consensus System</strong> and <strong>Microsoft</strong>.</p>
<p>Applicants must be from a traditionally underrepresented and/or marginalized group in the Web community, including but not limited to: persons identifying as LGBTQ, women, persons of color, and/or persons with disabilities; and be unable to attend without some financial assistance. Please <a href="https://www.w3.org/2002/09/wbs/1/diversity-scholarship-application-2018/">submit</a> or share with friends who qualify and might be interested, by <strong>15 July</strong>.</p>
<p>If your organization or yourself wishes to become a sponsor, please e-mail us!</p>
</div>
</div>
</div>
</div>
<p class="noprint"><span class="more-news"><a href="/blog/news/" title="More News">More news…</a> <a title="RSS feed for W3C home page news" href="/blog/news/feed" class="feedlink"><img width="30" height="30" alt="RSS" src="/2008/site/images/icons/rss30"></a> <a title="Atom feed for W3C home page news" href="/blog/news/feed/atom" class="feedlink"><img width="30" height="30" alt="Atom" src="/2008/site/images/icons/atom30"></a></span></p>
<div class="w3c_events_talks line">
<div class="unit size1on2 w3c_upcoming_talks" id="w3c_home_talks">
<h2 class="category"><a title="More Talks…" href="/Talks/">Talks and Appearances <img src="/2008/site/images/header-link" alt="Header link" width="13" height="13" class="header-link"></a></h2>
<ul class="vevent_list">
<li class="vevent">
<p class="date single"><span class="dtstart"><span class="year">2018</span><span class="mm-dd">-10-04</span></span> <span class="paren">(</span><span class="dd-mmm">04 OCT</span><span class="paren">)</span></p>
<div class="info-wrap">
<p class="summary"><a href="https://www.w3.org/blog/talks/event/le-w3c-pour-les-developeurs-web/" rel="bookmark">Le W3C pour les dévelopeurs Web</a></p>
<p class="source">by Dominique Hazael-Massieux</p>
<p class="eventtitle"><a href="https://www.w3.org/blog/talks/venue/ibm-client-paris/" title="IBM Client Paris">IBM Client Paris</a></p>
<p class="location">Bois-Colombes, France</p>
</div>
</li>
<li class="vevent">
<p class="date single"><span class="dtstart"><span class="year">2018</span><span class="mm-dd">-10-06</span></span> <span class="paren">(</span><span class="dd-mmm">06 OCT</span><span class="paren">)</span></p>
<div class="info-wrap">
<p class="summary"><a href="https://www.w3.org/blog/talks/event/le-projet-style-guide-ou-comment-fait-on-le-manuel-de-style-dun-site/" rel="bookmark">Le projet « Style Guide » ou comment fait-on le manuel de style d’un site ?</a></p>
<p class="source">by Bert Bos</p>
<p class="eventtitle"><a href="http://www.webschoolfactory.fr/">Web School Factory</a></p>
<p class="location">Paris, France</p>
</div>
</li>
<li class="vevent">
<p class="date single"><span class="dtstart"><span class="year">2018</span><span class="mm-dd">-10-18</span></span> <span class="paren">(</span><span class="dd-mmm">18 OCT</span><span class="paren">)</span></p>
<div class="info-wrap">
<p class="summary"><a href="https://www.w3.org/blog/talks/event/improving-advertising-on-the-web-a-w3c-initiative/" rel="bookmark">Improving Advertising on the Web, a W3C Initiative</a></p>
<p class="source"></p>
<p class="eventtitle"><a href="https://www.w3.org/blog/talks/venue/jacob-k-javits-convention-center/" title="Jacob K. Javits Convention Center">Jacob K. Javits Convention Center</a></p>
<p class="location">New York, United States</p>
</div>
</li>
</ul>
</div>
<div class="unit size1on2 lastUnit w3c_upcoming_events" id="w3c_home_upcoming_events">
<h2 class="category"><a title="More Events…" href="/participate/eventscal.html">Events <img src="/2008/site/images/header-link" alt="Header link" width="13" height="13" class="header-link"></a></h2>
<ul class="vevent_list">
<li class="vevent">
<div class="date"><span class="dtstart"><span class="year">2018</span><span class="mm-dd">-07-24</span></span> <span class="paren">(</span><span class="dd-mmm">24 JUL</span><span class="paren">)</span> <span class="date-separator">–</span> <span class="dtend"><span class="year">2018</span><span class="mm-dd">-07-26</span></span> <span class="paren">(</span><span class="dd-mmm">26 JUL</span><span class="paren">)</span></div>
<div class="info-wrap">
<p class="summary"><a href="https://github.com/w3ctag/meetings/tree/gh-pages/2018/07-seattle" class="uri url">Technical Architecture Group Meeting</a></p>
<p class="location">Seattle, WA, USA</p>
</div>
</li>
<li class="vevent">
<div class="date"><span class="dtstart"><span class="year">2018</span><span class="mm-dd">-07-26</span></span> <span class="paren">(</span><span class="dd-mmm">26 JUL</span><span class="paren">)</span> <span class="date-separator">–</span> <span class="dtend"><span class="year">2018</span><span class="mm-dd">-07-27</span></span> <span class="paren">(</span><span class="dd-mmm">27 JUL</span><span class="paren">)</span></div>
<div class="info-wrap">
<p class="summary"><a href="https://www.w3.org/community/credibility/2018/06/26/f2f2/" class="uri url">Credible Web Community Group</a></p>
<p class="location">San Francisco</p>
</div>
</li>
<li class="vevent">
<div class="date single"><span class="dtstart"><span class="year">2018</span><span class="mm-dd">-07-26</span></span> <span class="paren">(</span><span class="dd-mmm">26 JUL</span><span class="paren">)</span></div>
<div class="info-wrap">
<p class="summary"><a href="https://ti.to/w3c-tag/meet-the-tag-seattle" class="uri url">Meet the TAG</a></p>
<p class="location">Seattle, WA, USA</p>
<p class="host">Microsoft</p>
</div>
</li>
<li class="vevent">
<div class="date"><span class="dtstart"><span class="year">2018</span><span class="mm-dd">-09-18</span></span> <span class="paren">(</span><span class="dd-mmm">18 SEP</span><span class="paren">)</span> <span class="date-separator">–</span> <span class="dtend"><span class="year">2018</span><span class="mm-dd">-09-19</span></span> <span class="paren">(</span><span class="dd-mmm">19 SEP</span><span class="paren">)</span></div>
<div class="info-wrap">
<p class="summary"><a href="https://www.w3.org/publishing/events/tokyo18-workshop/" class="uri url">W3C Workshop on Digital Publication Layout and Presentation (from Manga to Magazines)</a></p>
<p class="location">Tokyo, Japan</p>
<p class="host">Hosted by Advanced Publishing Laboratory, Keio Research Institute</p>
</div>
</li>
<li class="vevent">
<div class="date"><span class="dtstart"><span class="year">2018</span><span class="mm-dd">-09-18</span></span> <span class="paren">(</span><span class="dd-mmm">18 SEP</span><span class="paren">)</span> <span class="date-separator">–</span> <span class="dtend"><span class="year">2018</span><span class="mm-dd">-09-19</span></span> <span class="paren">(</span><span class="dd-mmm">19 SEP</span><span class="paren">)</span></div>
<div class="info-wrap">
<p class="summary"><a href="https://www.w3.org/Privacy/permissions-ws-2018/cfp.html" class="uri url">W3C Workshop on Permissions and User Consent</a></p>
<p class="location">San Diego, California, USA</p>
<p class="host">Hosted by Qualcomm</p>
</div>
</li>
<li class="vevent">
<div class="date"><span class="dtstart"><span class="year">2018</span><span class="mm-dd">-09-26</span></span> <span class="paren">(</span><span class="dd-mmm">26 SEP</span><span class="paren">)</span> <span class="date-separator">–</span> <span class="dtend"><span class="year">2018</span><span class="mm-dd">-09-29</span></span> <span class="paren">(</span><span class="dd-mmm">29 SEP</span><span class="paren">)</span></div>
<div class="info-wrap">
<p class="summary"><a href="https://www.restfest.org/" class="uri url">REST Fest</a></p>
<p class="location">Greenville, SC, USA</p>
</div>
</li>
<li class="vevent">
<div class="date"><span class="dtstart"><span class="year">2018</span><span class="mm-dd">-10-04</span></span> <span class="paren">(</span> <span class="dd-mmm">4 OCT</span><span class="paren">)</span> <span class="date-separator">–</span> <span class="dtend"><span class="year">2018</span><span class="mm-dd">-10-06</span></span> <span class="paren">(</span> <span class="dd-mmm">6 OCT</span><span class="paren">)</span></div>
<div class="info-wrap">
<p class="summary"><a href="https://www.paris-web.fr/" class="uri url">Paris Web 2018</a></p>
<p class="location">Paris, France</p>
</div>
</li>
</ul>
</div>
</div>
</div>
</div>
<div class="unit size1on3 lastUnit">
<p class="about">The World Wide Web Consortium (W3C) is an international community that develops open <a href="/TR/">standards</a> to ensure the long-term growth of the Web.</p>
<p class="about">W3C operates under a <a href="/Consortium/cepc/">Code of Ethics and Professional Conduct</a>.</p>
<p class="about">Become a <a href="support/">Friend of W3C</a>: support the <a href="Consortium/mission">W3C mission</a> and free <a href="/developers/">developer tools</a>.</p>
<div id="w3c_home_recent_blogs">
<h2 class="category"><a title="More Blog Entries…" href="/blog/">W3C Blog <img src="/2008/site/images/header-link" alt="Header link" width="13" height="13" class="header-link"></a></h2>
<ul class="hentry_list">
<li class="hentry">
<p class="entry-title"><a href="https://www.w3.org/blog/2018/07/extended-submission-deadlines-for-the-workshop-on-digital-publication-layout-and-presentation/" class="uri url" rel="bookmark">Extended Submission Deadlines for the Workshop on Digital Publication Layout and Presentation</a></p>
<p class="date"><abbr title="2018-07-20" class="published">20 July 2018</abbr> by <span class="author vcard"><a class="fn url" href="http://www.w3.org/People/Ivan/">Ivan Herman</a></span></p>
</li>
<li class="hentry">
<p class="entry-title"><a href="https://www.w3.org/blog/2018/07/aria-1-2-fpwd/" class="uri url" rel="bookmark">Accessible Rich Internet Applications 1.2 suite published</a></p>
<p class="date"><abbr title="2018-07-19" class="published">19 July 2018</abbr> by <span class="author vcard">Joanmarie Diggs</span></p>
</li>
<li class="hentry">
<p class="entry-title"><a href="https://www.w3.org/blog/2018/07/exploring-css-property-definitions/" class="uri url" rel="bookmark">Exploring CSS property definitions</a></p>
<p class="date"><abbr title="2018-07-16" class="published">16 July 2018</abbr> by <span class="author vcard">François Daoust</span></p>
</li>
</ul>
</div>
<div id="w3c_home_new_jobs">
<h2 class="category"><a href="/Consortium/Recruitment/">Jobs <img src="/2008/site/images/header-link.gif" alt="Header link" width="13" height="13" class="header-link"></a></h2>
<p>We are hiring:</p>
<ul>
<li>A <a href="https://www.w3.org/Consortium/Recruitment/#job1">Web Standards Technology Expert</a> (Japan)</li>
<li>A <a href="https://www.w3.org/Consortium/Recruitment/#job2">Site Manager for W3C/Beihang</a> (China)</li>
</ul>
</div>
<div id="w3c_home_validators_software">
<h2 class="category"><a href="Status.html">Validators, More Software <img src="/2008/site/images/header-link.gif" alt="Header link" width="13" height="13" class="header-link"></a></h2>
<ul>
<li>Validators: <a title="W3C's Unified Validator" href="http://validator.w3.org/unicorn/">Unicorn</a>, <a title="HTML and XHTML Validator" href="http://validator.w3.org/">HTML</a>, <a title="CSS Validator" href="http://jigsaw.w3.org/css-validator/">CSS</a></li>
<li><a href="http://www.w3.org/2009/cheatsheet/">W3C cheatsheet</a></li>
<li><a href="Status.html">More Open Source Software</a></li>
</ul>
</div>
<div id="w3c_home_video">
<h2 class="category"><a href="https://www.w3.org/WAI/videos/standards-and-benefits.html">Web Accessibility and W3C standards (Video) <img src="/2008/site/images/header-link.gif" alt="Header link" width="13" height="13" class="header-link"></a></h2>
<p class="c1"><a href="https://www.w3.org/WAI/videos/standards-and-benefits.html"><img src="https://www.w3.org/blog/wp-content/uploads/2017/12/still.jpg" width="233" alt="Thumbnail of Web Accessibility and W3C Standards Video"></a></p>
<p>Watch our video on Web Accessibility and W3C standards!</p>
<h2 class="category"><a href="http://vimeo.com/w3c/buildstandards">Web Standards for the Future (Video) <img src="/2008/site/images/header-link.gif" alt="Header link" width="13" height="13" class="header-link"></a></h2>
<p class="c1"><a href="http://vimeo.com/w3c/buildstandards"><img src="/2014/10/stdvidthumb.png" alt="Thumbnail of Standards Video"></a></p>
<p>Check out our short video on Web standards!</p>
</div>
<div class="hpmt" id="w3c_home_member_testimonials">
<h2 class="category"><a title="Read all Member testimonials" href="/Consortium/Member/Testimonial/">W3C Member Testimonial <img src="/2008/site/images/header-link" alt="Header link" width="13" height="13" class="header-link"></a></h2>
<div id="w3c_home_member_testimonials_choice">
<p class="tPadding0"><a rel="nofollow" href="http://www.finanznachrichten.de" class="no-border"><img class="media" width="120" height="23" alt="FinanzNachrichten.de logo" src="/Consortium/Member/Testimonial/Logo/1061"></a></p>
<h3><a rel="nofollow" href="http://www.finanznachrichten.de">FinanzNachrichten.de</a></h3>
<p>FinanzNachrichten.de is the leading German speaking finance Website for financial news about shares, stock markets and economy. FinanzNachrichten.de as W3C member wants to take an active role in the further development of user friendly platform technologies for online media.</p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<div id="w3c_footer">
<div id="w3c_footer-inner">
<h2 class="offscreen">Footer Navigation</h2>
<div class="w3c_footer-nav">
<h3>Navigation</h3>
<ul class="footer_top_nav">
<li><a href="/">Home</a></li>
<li><a href="/standards/">Standards</a></li>
<li><a href="/participate/">Participate</a></li>
<li><a href="/Consortium/membership">Membership</a></li>
<li class="last-item"><a href="/Consortium/">About W3C</a></li>
</ul>
</div>
<div class="w3c_footer-nav">
<h3>Contact W3C</h3>
<ul class="footer_bottom_nav">
<li><a href="/Consortium/contact">Contact</a></li>
<li><a accesskey="0" href="/Help/">Help and FAQ</a></li>
<li><a href="/Consortium/sponsor/">Sponsor / Donate</a></li>
<li><a href="/Consortium/siteindex">Site Map</a></li>
<li>
<address id="w3c_signature"><a href="http://lists.w3.org/Archives/Public/site-comments/">Feedback</a></address>
</li>
</ul>
</div>
<div class="w3c_footer-nav">
<h3>W3C Updates</h3>
<ul class="footer_follow_nav">
<li><a href="http://twitter.com/W3C" title="Follow W3C on Twitter"><img src="/2008/site/images/Twitter_bird_logo_2012.svg" alt="Twitter" class="social-icon" height="40"></a></li>
</ul>
</div>
<p class="copyright">Copyright © 2018 W3C <sup>®</sup> (<a href="http://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>, <a href="http://www.ercim.eu/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>, <a href="http://www.keio.ac.jp/">Keio</a>, <a href="http://ev.buaa.edu.cn/">Beihang</a>) <a href="/Consortium/Legal/ipr-notice">Usage policies apply</a>.</p>
</div>
</div>
<div id="w3c_scripts">
<script type="text/javascript" src="/2008/site/js/main"></script></div>
</body>
</html>

Warnings Errors and Accessibility


Accessibility Checks:

line 591 column 1 - Access: [6.1.1.3]: style sheets require testing (style attribute).
line 595 column 1 - Access: [6.1.1.3]: style sheets require testing (style attribute).
line 8 column 1 - Access: [6.1.1.1]: style sheets require testing (link).
line 9 column 1 - Access: [6.1.1.2]: style sheets require testing (style element).
line 14 column 1 - Access: [6.1.1.1]: style sheets require testing (link).
line 16 column 1 - Access: [6.1.1.1]: style sheets require testing (link).
line 25 column 57 - Access: [2.1.1.1]: ensure information not conveyed through color alone (image).
line 25 column 57 - Access: [1.1.2.1]: <img> missing 'longdesc' and d-link.
line 71 column 11 - Access: [2.1.1.5]: ensure information not conveyed through color alone (input).
line 76 column 1 - Access: [3.6.1.1]: list usage invalid <ul>.
line 82 column 23 - Access: [2.1.1.5]: ensure information not conveyed through color alone (input).
line 82 column 23 - Access: [12.4.1.1]: associate labels explicitly with form controls.
line 82 column 154 - Access: [2.1.1.1]: ensure information not conveyed through color alone (image).
line 90 column 47 - Access: [2.1.1.1]: ensure information not conveyed through color alone (image).
line 90 column 47 - Access: [1.1.1.1]: <img> missing 'alt' text.
line 90 column 47 - Access: [1.1.2.1]: <img> missing 'longdesc' and d-link.
line 94 column 1 - Access: [7.1.1.5]: remove flicker (animated gif).
line 94 column 1 - Access: [2.1.1.1]: ensure information not conveyed through color alone (image).
line 95 column 88 - Access: [7.1.1.5]: remove flicker (animated gif).
line 95 column 88 - Access: [2.1.1.1]: ensure information not conveyed through color alone (image).
line 107 column 108 - Access: [7.1.1.5]: remove flicker (animated gif).
line 107 column 108 - Access: [2.1.1.1]: ensure information not conveyed through color alone (image).
line 114 column 103 - Access: [7.1.1.5]: remove flicker (animated gif).
line 114 column 103 - Access: [2.1.1.1]: ensure information not conveyed through color alone (image).
line 119 column 98 - Access: [7.1.1.5]: remove flicker (animated gif).
line 119 column 98 - Access: [2.1.1.1]: ensure information not conveyed through color alone (image).
line 124 column 88 - Access: [7.1.1.5]: remove flicker (animated gif).
line 124 column 88 - Access: [2.1.1.1]: ensure information not conveyed through color alone (image).
line 127 column 57 - Access: [2.1.1.1]: ensure information not conveyed through color alone (image).
line 127 column 57 - Access: [1.1.2.1]: <img> missing 'longdesc' and d-link.
line 128 column 77 - Access: [2.1.1.1]: ensure information not conveyed through color alone (image).
line 128 column 77 - Access: [1.1.2.1]: <img> missing 'longdesc' and d-link.
line 131 column 87 - Access: [7.1.1.5]: remove flicker (animated gif).
line 131 column 87 - Access: [2.1.1.1]: ensure information not conveyed through color alone (image).
line 142 column 35 - Access: [13.1.1.1]: link text not meaningful.
line 159 column 146 - Access: [7.1.1.5]: remove flicker (animated gif).
line 159 column 146 - Access: [2.1.1.1]: ensure information not conveyed through color alone (image).
line 159 column 146 - Access: [1.1.2.1]: <img> missing 'longdesc' and d-link.
line 183 column 165 - Access: [13.1.1.3]: link text too long.
line 185 column 76 - Access: [13.1.1.1]: link text not meaningful.
line 185 column 142 - Access: [13.1.1.1]: link text not meaningful.
line 213 column 138 - Access: [2.1.1.1]: ensure information not conveyed through color alone (image).
line 213 column 138 - Access: [1.1.2.1]: <img> missing 'longdesc' and d-link.
line 280 column 168 - Access: [2.1.1.1]: ensure information not conveyed through color alone (image).
line 280 column 168 - Access: [1.1.2.1]: <img> missing 'longdesc' and d-link.
line 282 column 177 - Access: [13.1.1.1]: link text not meaningful.
line 288 column 189 - Access: [2.1.1.1]: ensure information not conveyed through color alone (image).
line 288 column 189 - Access: [1.1.2.1]: <img> missing 'longdesc' and d-link.
line 288 column 359 - Access: [2.1.1.1]: ensure information not conveyed through color alone (image).
line 288 column 359 - Access: [1.1.2.1]: <img> missing 'longdesc' and d-link.
line 295 column 31 - Access: [2.1.1.1]: ensure information not conveyed through color alone (image).
line 330 column 24 - Access: [13.1.1.3]: link text too long.
line 368 column 158 - Access: [2.1.1.1]: ensure information not conveyed through color alone (image).
line 439 column 15 - Access: [13.1.1.3]: link text too long.
line 526 column 67 - Access: [2.1.1.1]: ensure information not conveyed through color alone (image).
line 531 column 13 - Access: [13.1.1.3]: link text too long.
line 568 column 22 - Access: [13.1.1.1]: link text not meaningful.
line 569 column 1 - Access: [7.1.1.5]: remove flicker (animated gif).
line 569 column 1 - Access: [2.1.1.1]: ensure information not conveyed through color alone (image).
line 580 column 10 - Access: [7.1.1.5]: remove flicker (animated gif).
line 580 column 10 - Access: [2.1.1.1]: ensure information not conveyed through color alone (image).
line 582 column 105 - Access: [13.1.1.1]: link text not meaningful.
line 582 column 183 - Access: [13.1.1.1]: link text not meaningful.
line 590 column 41 - Access: [7.1.1.5]: remove flicker (animated gif).
line 590 column 41 - Access: [2.1.1.1]: ensure information not conveyed through color alone (image).
line 591 column 99 - Access: [2.1.1.1]: ensure information not conveyed through color alone (image).
line 591 column 99 - Access: [1.1.2.1]: <img> missing 'longdesc' and d-link.
line 594 column 9 - Access: [7.1.1.5]: remove flicker (animated gif).
line 594 column 9 - Access: [2.1.1.1]: ensure information not conveyed through color alone (image).
line 595 column 77 - Access: [2.1.1.1]: ensure information not conveyed through color alone (image).
line 595 column 77 - Access: [1.1.2.1]: <img> missing 'longdesc' and d-link.
line 599 column 124 - Access: [2.1.1.1]: ensure information not conveyed through color alone (image).
line 602 column 13 - Access: [2.1.1.1]: ensure information not conveyed through color alone (image).
line 603 column 10 - Access: [1.1.2.1]: <img> missing 'longdesc' and d-link.
line 620 column 5 - Access: [13.1.1.1]: link text not meaningful.
line 642 column 68 - Access: [2.1.1.1]: ensure information not conveyed through color alone (image).
line 642 column 68 - Access: [1.1.2.1]: <img> missing 'longdesc' and d-link.
line 647 column 1 - Access: [13.1.1.1]: link text not meaningful.
line 653 column 1 - Access: [6.2.2.2]: text equivalents require updating (script).
line 653 column 1 - Access: [6.3.1.1]: programmatic objects require testing (script).
line 653 column 1 - Access: [8.1.1.1]: ensure programmatic objects are accessible (script).
line 653 column 1 - Access: [7.1.1.1]: remove flicker (script).
line 653 column 1 - Access: [2.1.1.4]: ensure information not conveyed through color alone (script).
line 653 column 1 - Access: [1.1.10.1]: <script> missing <noscript> section.
Info: Doctype given is "-//W3C//DTD XHTML 1.0 Strict//EN"
Info: Document content looks like XHTML 1.0 Strict
No warnings or errors were found.